-
Notifications
You must be signed in to change notification settings - Fork 96
✨ Add AdditionalArgs field to API for custom provider settings #782
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
✅ Deploy Preview for kubernetes-sigs-cluster-api-operator ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
2e3e4ba
to
3482300
Compare
Currently operator's API only allows to set common, most popular provider options. But sometimes it is necessary to specify non-standard options that the operator is not aware about. To do this we add a new API field called "AdditionalOptions" of type map[string]string. Every key there will be attached to provider's starting command.
3482300
to
18e9174
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
LGTM label has been added. Git tree hash: d3ad366536e55aa5b00ebb4b35ff80e8b1eb8b01
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexander-demicev 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:
The operator API previously supported only a predefined set of common provider options. This limited flexibility when working with less common or provider-specific configurations.
To address this, a new field AdditionalArgs of type map[string]string is introduced. Each key-value pair in this map will be passed directly to the provider’s startup command, enabling users to specify arbitrary flags or environment parameters not explicitly handled by the operator.
This change enhances extensibility without requiring frequent operator updates for niche use cases.
Fixes #587