-
Notifications
You must be signed in to change notification settings - Fork 4k
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
chore: defork labels and taints #7208
chore: defork labels and taints #7208
Conversation
Hi @charliedmcb. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Main changes lgtm. Is there anything in azure_template_test.go as well? |
There is another method in I still need to add testing as well. |
Ok, with the change to passing in
instead of having them within the function, this should be all the fork changes for both:
I'm going to look at adding some more testing though if easily possibly |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: charliedmcb, comtalyst 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 |
/hold |
/ok-to-test |
/cherry-pick cluster-autoscaler-1.29 |
@charliedmcb: only kubernetes org members may request cherry picks. If you are already part of the org, make sure to change your membership to public. Otherwise you can still do the cherry-pick manually. 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. |
/unhold |
/cherry-pick cluster-autoscaler-release-1.29 |
@comtalyst: once the present PR merges, I will cherry-pick it on top of cluster-autoscaler-release-1.29 in a new PR and assign it to you. 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. |
@comtalyst: new pull request created: #7215 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. |
/cherry-pick cluster-autoscaler-release-1.30 |
@comtalyst: new pull request created: #7216 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. |
/cherry-pick cluster-autoscaler-release-1.28 |
/cherry-pick cluster-autoscaler-release-1.27 |
@comtalyst: new pull request created: #7224 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. |
@comtalyst: new pull request created: #7225 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. |
/cherry-pick cluster-autoscaler-release-1.31 |
@comtalyst: new pull request created: #7240 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. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This is part of the deforking effort for Azure.
There are certain adjustments to the labels/taints process that make sense for consideration when constructing the node, and should be ported in for better accuracy.
This also, has some non-functional elements at the moment based on:
These are inputs that'll be allowed as Azure specific settings within the future to allow for additional, more accurate expectations of labels/taints.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
And the associated code are non-functional at the moment, but there will be a change coming down the line to make it functional. At the moment its just stubs to get the code in place, and should still work by taking the other still functional paths.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: