-
Notifications
You must be signed in to change notification settings - Fork 26
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
Expose configuration options for Openstack volumes in the template #967
Conversation
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, please bump the version in the config/dev/openstack-clusterdeployment.yaml
to the corresponding one
JFYI this patch solves #965 |
@MirgDenis do you want to add example config to config/dev/openstack-clusterdeployment.yaml ? Also, you might wish to update the k0rdent docs with the new configuration and add it to the OpenStack templates in the demo repo, perhaps as an additional demo or a template on Demo1? (In the "description" for your PR, you can add "Fixes: #965") and that should link it. |
@wkonitzer I think it's better to examples as simple as possible. For sure we will have more options added, maybe even all keys from OpenStackMachine will be added in template, so I think no point in one more example. Commit in doc is good idea, I will prepare a patch. |
@MirgDenis I disagree - I want to see an example of it somewhere so I'm not having to try and figure it out from all the docs, templates etc. I already have people interested in this update, so I'd like to make it as simple as possible for them (as non-coders), to get going. If there's a decent example in the docs template, that would be enough to keep me happy. |
@wkonitzer undertsood. But in my opinion there are no place for for such an example. config/dev has only one simplest scenario, and docs have only API ref.
And also examples can be grouped by control/worker attribute. I think such folder is out of scope of this PR. |
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. Please squash the commits.
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.
You should put new values into values.yaml
with an empty/default value. This is convention we're using for other charts, so please add it for consistency.
* Generate templates * Bump cluster template for openstack-clusterdeployment in config/dev * Fix descriptions in worker part of schema * Add default value for new key in values.yaml
Expose rootVolume option in Openstack standalone control plane cluster template.
Resolves #965