Open simonostendorf opened 1 year ago
Mh, I tried to figure out why its set this way, but it was introduced in the second commit of the repository without any comment: https://github.com/hetznercloud/hcloud-cloud-controller-manager/commit/785dd83c9390352acec09d5564934727bb1e3200#diff-b6264178c40e2a300a57855f7bbd1de74003cb68b4b9ac834432c73309f5c9bcR39
I think we can just remove it, in that case it would default to ClusterFirst
. Do you want to submit a PR?
Mh, I tried to figure out why its set this way, but it was introduced in the second commit of the repository without any comment: 785dd83#diff-b6264178c40e2a300a57855f7bbd1de74003cb68b4b9ac834432c73309f5c9bcR39
I think we can just remove it, in that case it would default to
ClusterFirst
. Do you want to submit a PR?
Thanks for your reply. Yes I can submit a PR.
There was an issue afterall with removing the DNS policy. I will try to find a solution that works for all cases.
This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.
I am using the hcloud cloud controller manager together with the istio sidecar proxy.
The istio proxy is stuck in a crash loop because it can't find the istiod host (
Error while dialing: dial tcp: lookup istiod.istio-system.svc on 185.12.64.1:53: no such host
). This is using the hetzner dns here (where obviously the entry can not be found).If I switch the dnsPolicy inside the deployment to
ClusterFirst
everything works as expected.Is there a reason why it is configured to use
Default
?See here, here, here and here.