-
Notifications
You must be signed in to change notification settings - Fork 178
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
Initial implementation for YAML based config #305
Conversation
0eaf212
to
34854f4
Compare
The lint test/check is failing because of the struct names ConfigINI and ConfigYAML, but I would like to keep these names as-is for now because this is only temporary since this also has a future deprecation notice for the INI-based configuration. If it's an issue, I can change the class names to just INI and YAML as recommends.
The integration test is failing for some unknown reason. I think it might be some issue with the timing when cluster coming up in the test or perhaps the verification that it's deployed correctly. See below:
I looking into the integration test failure right now... |
34854f4
to
f070ca0
Compare
@andrewsykim we just have the one item/flag left... I can change it either way. If we do change it back, it would be preferred if the newer YAML at least matches. |
3d9bbe5
to
5654e42
Compare
/retest |
b3a8579
to
0ea6e5f
Compare
I took another pass at reviewing this PR and I think it looks good... and all current feedback has been addressed. |
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.
Is the virtualcenter -> vcenter technically a breaking change? I agree on the name change but both field name should be accepted I think?
fbcbf0f
to
d149dac
Compare
There are some changes (port from string to unit) that I want to retest with before giving my "thumbs up" again for additional review and/or merge. |
65a2b29
to
5d3cb31
Compare
Tested on a 1.17.4 config with my normal config of 2 VCs with 3DCs cut into 3 zones... looks good to me! Good for another pass @andrewsykim |
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, minor comments about using camel case in documentation
docs/book/tutorials/deploying_cpi_and_csi_with_multi_dc_vc_aka_zones.md
Outdated
Show resolved
Hide resolved
Fix lint and format Fixing go tests Update go tests Add more go tests Change package name Fixed docs Fix go test virtualcenter -> vcenter in docs Fixed YAML camel case Update for lint Fixes based on feedback Fix config YAML
4372a8f
to
ab57b53
Compare
Updated based on latest feedback from @andrewsykim |
@@ -26,7 +30,7 @@ spec: | |||
nodeSelector: | |||
node-role.kubernetes.io/master: "" | |||
securityContext: | |||
runAsUser: 0 |
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.
Are the changes in this file intentional?
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.
yes, it is. I forgot to pull down the YAML I used to test with. There were discrepancies between the vsphere-cloud-controller-manager-ds.yaml and vsphere-cloud-controller-manager-pod.yaml. This resolves it... the ds.yaml should be running as user 1001 which is a non-root account.
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.
Should have been changed for this PR:
#297
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewsykim 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 |
What this PR does / why we need it:
Implements a new YAML-based cloud-config which will enable a bunch of new features going forward:
Which issue this PR fixes: fixes #275
Special notes for your reviewer:
go test
to verify functionalityRelease note:
Since this PR preserves backward compatibility of the INI-based cloud-config (and has been tested), this should have little impact (as of right now) to the end-user.