-
Notifications
You must be signed in to change notification settings - Fork 192
Support adding node labels for control plane nodes when cluster creation for vsphere/aws/azure #3818
Conversation
Cluster Generation A/B Results: |
Codecov Report
@@ Coverage Diff @@
## main #3818 +/- ##
==========================================
- Coverage 47.64% 46.79% -0.85%
==========================================
Files 420 445 +25
Lines 42080 43669 +1589
==========================================
+ Hits 20051 20437 +386
- Misses 20112 21306 +1194
- Partials 1917 1926 +9
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
8e7853d
to
c720ce6
Compare
Cluster Generation A/B Results: |
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.
This will still break the node pools cli implementation. This fix will either be to get tkgs on board with this style of adding nodeLabels or have the node pool cil implementation handle two sets of nodeLabels/nodePoolLabels. Either way, I won't have time to implement this before Friday. I'm hoping to have some help from you in updating the implementation. Please file a P0 bug to track this for FC
c720ce6
to
a2e8819
Compare
Latest test result after commit Ignore worker.nodeLabels if nodePoolLabels is set
The worker.nodeLabels |
Cluster Generation A/B Results: |
Summarize a discussion with @tenczar offline, Nick mentioned that in legacy cluster mode nodePoolLabels will replace worker labels set by ytt overlay, but what I thought those 2 types of labels are to be merged, which is wrong, to maintain backward compatibility, I add commit Ignore worker.nodeLabels if nodePoolLabels is set. |
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.
I would love to set up a chat with a PM about this, who is it and when can we have this meeting?
Hi @tenczar , just let you know, I raised the issue in our scrum, and we prefer to hold the PR since we don't want to touch TKGs. |
a2e8819
to
f43a7b4
Compare
Cluster Generation A/B Results: |
After discuss with @DanielXiao , we think it's better to drop this, since control plane node label seems non-trivial, and worker node label is equivalent to nodePoolLabels, as PM also want to keep consistent between TKGm and TKGs. No need to add this PR to increase complexity. Hence close it now. |
f43a7b4
to
f236302
Compare
Reopen it since Timmy explicitly require to add the control plane node labels back, the worker.Labels will be just use nodePoolLabels as alternative. |
Cluster Generation A/B Results: |
Cluster Generation A/B Results: |
f236302
to
2e75bea
Compare
Cluster Generation A/B Results: |
2e75bea
to
566b666
Compare
Cluster Generation A/B Results: |
566b666
to
8deb9f2
Compare
Cluster Generation A/B Results: |
Just finished manually testing for AWS cluster creation with latest code, though the cluster cannot be created due to feature-gate issue, I could see the labels are correct on KCP:
|
What this PR does / why we need it
Add
CONTROL_PLANE_NODE_LABELS
param to support adding labels for control plane nodes upon cluster creation.Which issue(s) this PR fixes
Fixes #3616
Describe testing done for PR
Manually created cluster with below variables set:
The result on vSphere:
The result on AWS:
The result on Azure:
Release note
Additional information
Special notes for your reviewer