-
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
Revert "Add EC2 instance lifecycle label to nodes" #9162
Conversation
This reverts commit 7f2f195
We currently handle this with our own controller that adds a "node-labeler.granular.ag/spot" label to the nodes.. I can see where kops would want to add other node labels in the future.. Should use do something like "node-labeler.kops.k8s.io/spot-worker".. That would avoid the reuse of the "node-role.kubernetes.io" which was raised as a concern and establish a good pattern if we need to add more.. P.S. Would love to see this in 1.17.... |
/retest |
SSL error sounds super odd... /retest |
GH outage... /retest |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: johngmyers, 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 |
Not sure if the decision was actually to revert it. I see in the notes:
Is it such a big deal if 1.17 ships with this as it was? |
This reverts commit 7f2f195 cherrypicked in through #9152.
Concern was raised during Kops Office Hours as to the naming of the label. I propose we revert this change from 1.17 to give us until 1.18 to resolve the naming decision.