Skip to content
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

Merged
merged 1 commit into from
May 22, 2020

Conversation

johngmyers
Copy link
Member

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.

@k8s-ci-robot k8s-ci-robot added this to the v1.17 milestone May 22, 2020
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels May 22, 2020
@k8s-ci-robot k8s-ci-robot requested review from gambol99 and justinsb May 22, 2020 18:25
@granular-ryanbonham
Copy link
Contributor

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....

@johngmyers
Copy link
Member Author

/retest

@chrisz100
Copy link
Contributor

SSL error sounds super odd...

/retest
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 22, 2020
@rifelpet
Copy link
Member

GH outage...

/retest

@rifelpet
Copy link
Member

/retest

@rifelpet
Copy link
Member

/approve

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 22, 2020
@k8s-ci-robot k8s-ci-robot merged commit 1c9ca79 into kubernetes:release-1.17 May 22, 2020
@johngmyers johngmyers deleted the revert-9152 branch May 22, 2020 23:42
@hakman
Copy link
Member

hakman commented May 23, 2020

Not sure if the decision was actually to revert it. I see in the notes:

Decision: used by k8s spot termination handler tool, so probably not renaming label

Is it such a big deal if 1.17 ships with this as it was?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants