-
Notifications
You must be signed in to change notification settings - Fork 37
Add configEnabled values to toggle CM creation #108
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
Conversation
7bc48e6
to
98b93e3
Compare
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.
The change looks straightforward enough and upgrade scenarios should be handled OK as well since configEnabled
will not be passed explicitly (as it didn't exist on previous versions of the chart) and will then get is default true
value (unless explicitly set to false
).
Given limited usage of this field, especially in Rancher use cases, it's fine to not add it to questions.yaml
.
98b93e3
to
1d2e3a7
Compare
c69e159
to
84576ae
Compare
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!
Final nit: bump the version in Chart.yaml
84576ae
to
87a159f
Compare
Signed-off-by: Alexandr Demicev <[email protected]>
87a159f
to
1c57915
Compare
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.
We don't do "releases" on this repo. |
Sorry if I was not clear. I was wondering where the chart is/will be published, including the changes in this PR |
Pull Request Checklist
Types of Change
Add configEnabled values to toggle CM creation, this allows users to pass their own. The change is similar to upstream chart feature https://github.com/kubernetes/cloud-provider-vsphere/blob/master/charts/vsphere-cpi/templates/configmap.yaml#L7
Linked Issues
Additional Notes
After the PR is merged
Once the PR is merged, typically upon a new release, the necessary teams will be notified via Slack hook to perform the RKE2 Charts and RKE2 changes. Any developer working on this issue is not responsible for updating RKE2 Charts or RKE2.