-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Only set NTH ManagedASGTag label if it doesn't already exist #17141
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
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman 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 |
…41-origin-release-1.31 Automated cherry pick of #17141: Only set NTH ManagedASGTag label if it doesn't already exist
…41-origin-release-1.30 Automated cherry pick of #17141: Only set NTH ManagedASGTag label if it doesn't already exist
/test all |
/retest |
/override pull-kops-e2e-k8s-aws-amazonvpc |
@hakman: Overrode contexts on behalf of hakman: pull-kops-e2e-k8s-aws-amazonvpc 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. |
Reported on slack.
If a cluster has ManagedASGTag set to an existing label, it is overwritten with an empty value. For the
kubernetes.io/cluster/$cluster
tag, this can cause problems during cluster deletion.NTH doesn't actually care about the value of the tag:
https://github.com/aws/aws-node-termination-handler/blob/a0c0aa1bd14780b0d5ca7ce70cd92eed746ff64d/pkg/monitor/sqsevent/sqs-monitor.go#L427-L431
So if the tag is already set then we should preserve its existing value.