[Feature Request] Support K3s/RKE option --data-dir #329
Labels
No labels
🐛 bug
DO THE THING >:(
blocked
dependencies
k3s
kind
openbao
question
secrets
wontfix
✨ enhancement
🌱good first issue
📓documentation
📕kyverno
🔐 Bitwarden
🙋help wanted
🦩 MinIO
🧸 🧸 Duplicate
🩹 Bug Fix
🪠 CICD
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
small-hack/smol-k8s-lab#329
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the feature you'd like, and why
K3s and other SUSe k8s distros accept the option
--data-dirwhich 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-dirhas been specified underk8s_distros.k3s.k3s_yaml.data-dirin the config file. this leads to the following error when attaching a new node: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/rancherwhich can cause unexpected disk-pressure issues.