-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
dns: use resolved region rather than re-resolving every time #16778
Conversation
/hold As I'm not very sure about this |
I want to make sure we dont reintroduce #16645 My initial idea for this fix was to only include the |
Ah - that does sound like a better approach than mine here! Do you want to send a PR, or if you want I can adapt this one? |
Feel free to test my theory in this PR :) |
This should allow use to IMDS on EC2, but not when not running on EC2, for example when running `kops update cluster`.
/retest pull-kops-e2e-k8s-aws-amazonvpc |
@rifelpet: The
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test pull-kops-e2e-k8s-aws-amazonvpc |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold |
Looks like this didn't fix the problem:
|
…78-origin-release-1.30 Automated cherry pick of #16778: dns: don't use IMDS region resolver when it previously failed
This should allow the fallback behaviour to work as expected.