-
Notifications
You must be signed in to change notification settings - Fork 210
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
Switch pod to world testing from cilium.io
to one.one.one.one
#511
Conversation
558b09b
to
a705db7
Compare
Will "client-egress-to-fqdns-cilium-io.yaml" need to be updated?
|
You are right, I missed that one. |
Tentative fix for #367. We have two main hypothesis around why connections to external domains are flaky: - The external domain itself is unreliable. - The external domain works fine, but CoreDNS is unreliable. `cilium.io` is hosted on single non-HA EC2 instance, which is definitely the most robus thing out there. We propose switching to `one.one.one.one` as a quick fix to check if that helps with the reliability. If yes, we will evaluate moving to a HA system that we control ourselves (e.g. a DNS zone hosted at a major provider). If not, we will investigate the CoreDNS hypothesis. Signed-off-by: Nicolas Busseneau <[email protected]>
a705db7
to
6d4e16a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not believe this will fix our flakes as you're aware from my recent update to the flake issue proper, but I do think this is a good idea none-the-less.
Tentative fix for #367.
We have two main hypothesis around why connections to external domains are flaky:
cilium.io
is hosted on single non-HA EC2 instance, which is definitely the most robus thing out there. We propose switching toone.one.one.one
as a quick fix to check if that helps with the reliability.If yes, we will evaluate moving to a HA system that we control ourselves (e.g. a DNS zone hosted at a major provider).
If not, we will investigate the CoreDNS hypothesis.