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
This seems to make sense to me as the Agent ensures connectivity of the control-plane to all nodes kubelets. This way nodes in isolated network zones can still be contacted by the contol-plane. Which is the use-case I am intending to use it for.
@kvaps Does it make sense to adopt the DaemonSet style?
Thank you very much for the hard work put in so far.
The text was updated successfully, but these errors were encountered:
Hi there,
Thank you for this great helm chart!
I noticed that Kubernetes Documentation states running the Konnectivity Agent as a DaemonSet rather than a Deployment.
https://kubernetes.io/docs/tasks/extend-kubernetes/setup-konnectivity/
https://raw.githubusercontent.com/kubernetes/website/main/content/en/examples/admin/konnectivity/konnectivity-agent.yaml
This seems to make sense to me as the Agent ensures connectivity of the control-plane to all nodes kubelets. This way nodes in isolated network zones can still be contacted by the contol-plane. Which is the use-case I am intending to use it for.
@kvaps Does it make sense to adopt the DaemonSet style?
Thank you very much for the hard work put in so far.
The text was updated successfully, but these errors were encountered: