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

fix(deployment): remove dns-policy #560

Merged
merged 1 commit into from
Nov 14, 2023
Merged

fix(deployment): remove dns-policy #560

merged 1 commit into from
Nov 14, 2023

Conversation

simonostendorf
Copy link
Contributor

@simonostendorf simonostendorf commented Nov 13, 2023

Closes #559

BEGIN_COMMIT_OVERRIDE
chore(deployment): remove dns-policy (later reverted)
END_COMMIT_OVERRIDE

@simonostendorf simonostendorf requested a review from a team as a code owner November 13, 2023 13:32
Copy link
Member

@apricote apricote left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ran the e2e tests locally, all looking good :) Thanks for the fix @simonostendorf!

@apricote apricote merged commit 2c83786 into hetznercloud:main Nov 14, 2023
3 of 7 checks passed
@apricote
Copy link
Member

This has caused a regression in our dev/test system for Deployments not using the Network Routes (#561):

  1. Cluster is initialized
  2. CoreDNS is not starting because the Node is still tainted with node.cloudprovider.kubernetes.io/uninitialized
  3. HCCM is deployed, but can not initialize Node because it needs to resolve the domain api.hetzner.cloud with CoreDNS. This fails with Get "https://api.hetzner.cloud/v1/servers?": dial tcp: lookup api.hetzner.cloud: i/o timeout
  4. => Deadlock

I am going to revert this for now to (finally) get #561 in, then we can take another look at how we can improve the situation for your sidecars.

apricote added a commit that referenced this pull request Nov 21, 2023
This reverts commit 2c83786.

The commit caused a regression where clusters not using the host
network were unable to bootstrap successfully:

- CoreDNS did not start because the Node was still tainted as
  uninitalized
- HCCM could not initialize the Node because it failed to resolve the
  DNS entry for "api.hetzner.cloud".
apricote added a commit that referenced this pull request Nov 21, 2023
This reverts commit 2c83786 / #560.

The commit caused a regression where clusters not using the host network
were unable to bootstrap successfully:

- CoreDNS did not start because the Node was still tainted as uninitalized
- HCCM could not initialize the Node because it failed to resolve the DNS entry for "api.hetzner.cloud".
@simonostendorf
Copy link
Contributor Author

simonostendorf commented Feb 16, 2024

I am going to revert this for now to (finally) get #561 in, then we can take another look at how we can improve the situation for your sidecars.

Are there any news @apricote ?

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

Successfully merging this pull request may close these issues.

DnsPolicy results in crashing istio proxy
2 participants