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

"genie-network-admission-controller" must be running on master nodes only? What if we're deploying on managed kubernetes? #215

Closed
shinebayar-g opened this issue Dec 23, 2020 · 0 comments

Comments

@shinebayar-g
Copy link

shinebayar-g commented Dec 23, 2020

Hi. We're deploying CNI-Genie on our production. On genie-network-admission-controller DaemonSet file it says

# Genie network admission controller daemonset configuration
# Genie network admission controller pods will run only in master nodes
kind: DaemonSet
apiVersion: apps/v1
metadata:
name: genie-network-admission-controller
namespace: kube-system
labels:
role: genie-network-admission-controller
Does it mean this daemonset must be running only on master nodes, or it could run on worker nodes if the master node isn't available like every other managed kubernetes service?

I didn't know this daemonset wasn't running any pods until today. CNI-Genie plugin worked without it. What's gonna be missing if I don't deploy this at all?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant