-
Notifications
You must be signed in to change notification settings - Fork 192
Fix template issues in vsphere clusterclass implementation #3173
Conversation
4433ebe
to
17f54a2
Compare
Cluster Generation A/B Results: |
Cluster Generation A/B Results: |
fed3b3c
to
276383f
Compare
Cluster Generation A/B Results: |
276383f
to
4ccd9a8
Compare
Cluster Generation A/B Results: |
Cluster Generation A/B Results: |
b509df4
to
e194a3e
Compare
Cluster Generation A/B Results: |
e194a3e
to
d8bde5d
Compare
Cluster Generation A/B Results: |
pkg/v1/providers/config_default.yaml
Outdated
@@ -174,9 +174,9 @@ NSXT_PASSWORD: "" | |||
#! NSX-T host | |||
NSXT_MANAGER_HOST: "" | |||
#! set this to true if NSX-T uses self-signed cert | |||
NSXT_ALLOW_UNVERIFIED_SSL: "false" | |||
NSXT_ALLOW_UNVERIFIED_SSL: false |
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.
@tenczar : this change enables legacy config file not specifying this value to work correctly with the vsphere CC, but this changes the behavior when we need to use the equivalent legacy config file in fallback (pure client side ytt) mode.
Either existing logic that assumed string instead of bool will have to be updated (see ytt/02_addons/cpi/cpi_addon_data.lib.yaml and associated vendir-ed code)
or we should consider retaining the definition/semantics of the variables in config_default.yaml (and fixing on the yttcc side to translate the string to bool)
(same for NSXT_REMOTE_AUTH)
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.
Either existing logic that assumed string instead of bool will have to be updated (see ytt/02_addons/cpi/cpi_addon_data.lib.yaml and associated vendir-ed code)
If we change the existing logic, will the upgrade break, since customer's previous value is still string
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.
Thanks for reminding me. We will look for convertion for CC to avoid breaking existing logic.
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.
If we change the existing logic, will the upgrade break, since customer's previous value is still string
@lubronzhan if we elect to change the legacy overlays for handling cpi addons, it will have to be done in a way that accepts both a string and a bool to not break upgrade (or when we need to fallback to legacy creation, for that matter)
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.
@vuil Yeah that's my concern, since we can't break customer's upgrade path.
e6b15c3
to
2c1c825
Compare
Cluster Generation A/B Results: |
Cluster Generation A/B Results: |
Cluster Generation A/B Results: |
2c1c825
to
741aaef
Compare
Cluster Generation A/B Results: |
741aaef
to
1de66e6
Compare
Cluster Generation A/B Results: |
1de66e6
to
4f0c972
Compare
Cluster Generation A/B Results: |
4f0c972
to
595d6c4
Compare
Cluster Generation A/B Results: |
595d6c4
to
2dd7bfb
Compare
Cluster Generation A/B Results: |
Codecov Report
@@ Coverage Diff @@
## main #3173 +/- ##
==========================================
+ Coverage 53.12% 53.66% +0.54%
==========================================
Files 103 91 -12
Lines 10419 10002 -417
==========================================
- Hits 5535 5368 -167
+ Misses 4429 4193 -236
+ Partials 455 441 -14
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
2dd7bfb
to
d001524
Compare
Cluster Generation A/B Results: |
Fix missing config_default values add missing "USE_TOPOLOGY_CATEGORIES" config variable with default value of false. properly convert boolean values to bool in clusterbootstrap.yml Use kube-vip specific imageRepository for deploying kube-vip ccluster gen hack to add resolve-os-image Fix cb secret handling fix indentation in vpshere machine template network defintion updates patches so node-labels avoid adding illegal labels
d001524
to
fbdb2bf
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.
Looks good. Thanks @tenczar! (for the change and for your patience)
What this PR does / why we need it
This PR updates ytt and go text templates for vsphere clusterclass that prevented successful deployment of clusterclass based capv clusters. Changes include:
Which issue(s) this PR fixes
Fixes #3439
Describe testing done for PR
Manually deployed a clusterclass based management cluster using Antrea and validated that the cluster is created successfully.
Release note
Additional information
Special notes for your reviewer