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

CordeDNS daemonset cannot be mutated #1660

Open
hajnalmt opened this issue Oct 11, 2024 · 0 comments
Open

CordeDNS daemonset cannot be mutated #1660

hajnalmt opened this issue Oct 11, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@hajnalmt
Copy link

Description

First off, thank you for creating and maintaining this awesome project!

After applying policy-controller on our infra namespaces we realized a kind of Chicken-Egg problem with CoreDNS and Policy-controller. The problem is that the policy-controller's service name cannot be resolved without a CoreDNS pod running, but the CoreDNS replicasets and pods cannot start, since they can't be mutated because the service which the MutatingWebhook calls cannot be resolved. Of course, we temporarily removed the flag from the namespace added it back after the pods have started, and rollout restarted everything but this will come up as a problem again in any cluster shutdown or disaster recovery scenario.

Do you have any suggestions to solve this somehow?
Thank you in advance!

@hajnalmt hajnalmt added the enhancement New feature or request label Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant