Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

konnectivity-agent as DaemonSet #15

Closed
sspreitzer opened this issue Jun 26, 2022 · 1 comment · Fixed by #18
Closed

konnectivity-agent as DaemonSet #15

sspreitzer opened this issue Jun 26, 2022 · 1 comment · Fixed by #18

Comments

@sspreitzer
Copy link

sspreitzer commented Jun 26, 2022

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.

@sspreitzer
Copy link
Author

I figured that increasing the replicas to an amount > count of nodes is a workaround

This was referenced Feb 9, 2023
@kvaps kvaps closed this as completed in #18 Feb 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant