Skip to content
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

Update default rke2 configuration file path #475

Open
sebastienmusso opened this issue Oct 20, 2024 · 0 comments
Open

Update default rke2 configuration file path #475

sebastienmusso opened this issue Oct 20, 2024 · 0 comments
Labels
kind/feature New feature or request needs-priority Indicates an issue or PR needs a priority assigning to it needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@sebastienmusso
Copy link

Describe the solution you'd like:
Rke2 configuration file path is Defined with static and cannot be override (

)
It mean that all spécific rke2 node configuration have to update this yaml file wich can be tricky

Why do you want this feature:

It should be interesting to update de default file location to /etc/rancher/rke2/config.yamld/50-capi.yaml
In order to give the ability to create other custom file wich will be nativelly marged by rke2 binary
or give the ability to the user to chose the filepath within rke2controlplane crd Spec.

Anything else you would like to add:
I would like to do the pull request but changing default file path location could break users configuration and add custom parameter crd field could increase code complexity.

how could we improve customization in a simple way ?

@sebastienmusso sebastienmusso added kind/feature New feature or request needs-priority Indicates an issue or PR needs a priority assigning to it needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request needs-priority Indicates an issue or PR needs a priority assigning to it needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

1 participant