You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2023. It is now read-only.
Currently, the only notifier implementation is a stub called no-op. This by itself is not very useful, as applications relying on the tree will need to be notified when a node or a set of nodes from the tree are deleted.
The idea is to implement a notifier driver that notifies clients a light weight and long lived GRPC connection.
This is useful for client applications that may reside in the same pod as the tree manager when deploying as a container in Kubernetes.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, the only notifier implementation is a stub called
no-op
. This by itself is not very useful, as applications relying on the tree will need to be notified when a node or a set of nodes from the tree are deleted.The idea is to implement a notifier driver that notifies clients a light weight and long lived GRPC connection.
This is useful for client applications that may reside in the same pod as the tree manager when deploying as a container in Kubernetes.
The text was updated successfully, but these errors were encountered: