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

[Feature Request] Support K3s/RKE option --data-dir #329

Open
cloudymax opened this issue Oct 26, 2024 · 0 comments
Open

[Feature Request] Support K3s/RKE option --data-dir #329

cloudymax opened this issue Oct 26, 2024 · 0 comments
Labels
✨ enhancement New feature request

Comments

@cloudymax
Copy link
Collaborator

Describe the feature you'd like, and why

K3s and other SUSe k8s distros accept the option --data-dir which allows a user to specify an alternative location for k3s data to be stored (replaces /var/lib/rancher)

Currently, when we connect new nodes to the cluster, we check the default location even if data-dir has been specified under k8s_distros.k3s.k3s_yaml.data-dir in the config file. this leads to the following error when attaching a new node:

 > cat: /var/lib/rancher/k3s/server/node-token: No such file or directory

Describe alternatives you've considered, if any

This can sort-of be worked around by specifying a new storage class for local-path provisioned that points tot he desired directory but that will still leave the core k3s components installed to /var/lib/rancher which can cause unexpected disk-pressure issues.

@cloudymax cloudymax added the ✨ enhancement New feature request label Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ enhancement New feature request
Projects
None yet
Development

No branches or pull requests

1 participant