-
Notifications
You must be signed in to change notification settings - Fork 131
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
Remove DisableStrictZoneCheck from AWS 1.27 cloud-config #1638
Conversation
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.
/approve
We'll need the same changes in OSM as well @xrstf
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik, xrstf 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 |
LGTM label has been added. Git tree hash: 363a0d86eddca495ab2769682239dba3316affc8
|
/lgtm |
LGTM label has been added. Git tree hash: a3512e31e15997e8cc2d0e019cc6fa790f17b7ab
|
/retest |
/override pull-machine-controller-e2e-aws-spot-instance AWS is out of capacity for spot instances. |
@xrstf: Overrode contexts on behalf of xrstf: pull-machine-controller-e2e-aws-spot-instance, pull-machine-controller-e2e-aws-spot-instance-legacy-userdata 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/test-infra repository. |
What this PR does / why we need it:
kubernetes/cloud-provider-aws#573 removed the
DisableStrictZoneCheck
field alltogether from the cloud-config. The new CCM will reject and fail to load an old cloud-config, so we must ensure that the field is not part of the cloud-config at all.This PR achieves this by only rendering the field if it's enabled, shifting the burden to set it properly onto our consumers.
What type of PR is this?
/kind bug
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: