-
Notifications
You must be signed in to change notification settings - Fork 87
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
⚠️ ✨ Make helm chart values extensible per component #638
base: main
Are you sure you want to change the base?
Conversation
Welcome @rbjorklin! |
Hi @rbjorklin. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
✅ Deploy Preview for kubernetes-sigs-cluster-api-operator ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/ok-to-test |
@rbjorklin hey, would you be able to look into failing CI tests and fix them, so that we can start reviewing it ? |
The intention is to reduce time to comprehension of the chart.
0eeb087
to
d297aca
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
6d5c42b
to
1691bc3
Compare
This commit breaks the colon separated string into multiple key-value pairs. This is in preparation for extension points to the chart. BREAKING CHANGE: This changes the format of the values.yaml file. Chart uses must make adaptations.
1691bc3
to
d22f12b
Compare
Fixed, please take a look! |
core: {} | ||
# name: "" | ||
# namespace: "" # Optional | ||
# version: "" # Optional |
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 is currently not a list because:
Note: Only one CoreProvider can be installed at the same time on a single cluster.
But maybe it should be a singleton list just to align it with the others?
@furkatgofurov7 given that this changes the structure of |
What this PR does / why we need it:
When deploying clusters to AKS using Workload Identity an annotation is required on the service account and a label is required on the pod. By extending the chart to expose the already existing functionality to patch provider manifests this PR allows for setting up AKS clusters using Workload Identity.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #