-
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
Also set new (non-beta/non-deprecated) labels in buildGenericLabels #4053
Conversation
Welcome @codablock! |
I see that 1.21 is underway. Is there a chance to still get this into 1.21? It might also make sense to backport this to older versions, as it looks like all versions are affected by this. |
After looking into other cloud providers, I realised that all cloud providers have this same issue. I decided to reimplement the solution in a generic way (based on updateDeprecatedTemplateLabels) and force-pushed this. |
Thanks for the PR and putting in the work to make it a generic solution. There's a couple of AWS related conflicts after the merging of #3848, however other than it looks good to me from the AWS side. |
@gjtempleton fyi, I've resolved the merge conflicts in the meantime. |
@gjtempleton Hello. Just wanted to check if there is any update on planning to merge this one? My understand is that we're ready for merge. |
Sorry for the delay! Thanks for the nudge. All looks good on the AWS side. You'll still need approval from one of the higher-level approvers of the wider CA codebase as well as mentioned by the CI-robot, I'm only an approver on the AWS cloud provider code. |
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.
overall this looks nice to me, just a minor spacing issue on the tests, otherwise i'm /lgtm
And at the same time only set stable labels in all buildGenericLabels implementations. This fixes issues when a node group has 0 nodes yet and node labels are built using buildGenericLabels and the node-template labels. Issues include (anti-)affinity and nodeSelectors for the given labels, giving false-negative results for candidate nodes, which leads to ASGs never scaling up.
arch is not hardcoded anymore
thanks @codablock ! |
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.
LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: codablock, feiskyer 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 |
Also set new (non-beta/non-deprecated) labels in buildGenericLabels
Also set new (non-beta/non-deprecated) labels in buildGenericLabels
Also set new (non-beta/non-deprecated) labels in buildGenericLabels
Also set new (non-beta/non-deprecated) labels in buildGenericLabels
Also set new (non-beta/non-deprecated) labels in buildGenericLabels
Also set new (non-beta/non-deprecated) labels in buildGenericLabels
This fixes issues when an ASG has 0 nodes yet and node labels are built
using buildGenericLabels and the node-template labels.
Issues include (anti-)affinity and nodeSelectors for the given labels,
giving false-negative results for candidate nodes, which leads to ASGs
never scaling up.