rancher: use a zfs dataset for /var/lib/kubelet to use the local storage for EmptyDir volumes
Closed
requested to merge generated-differential-D8482-source into generated-differential-D8482-target
A manual reconfiguration of the existing nodes will be needed to configure the dataset beforepuppet does a mount over on the existing directory content
Related to T4506
Test Plan
diff origin/production/rancher-node-staging-worker1.internal.staging.swh.network current/rancher-node-staging-worker1.internal.staging.swh.network
*******************************************
+ Zfs[data/kubelet] =>
parameters =>
"atime": "off",
"compression": "zstd",
"ensure": "present",
"mountpoint": "/var/lib/kubelet"
*******************************************
*** End octocatalog-diff on rancher-node-staging-worker1.internal.staging.swh.network
but also
diff origin/production/rancher-node-production-worker01.internal.softwareheritage.org current/rancher-node-production-worker01.internal.softwareheritage.org
*******************************************
+ Zfs[data/kubelet] =>
parameters =>
"atime": "off",
"compression": "zstd",
"ensure": "present",
"mountpoint": "/var/lib/kubelet"
*******************************************
*** End octocatalog-diff on rancher-node-production-worker01.internal.softwareheritage.org
Migrated from D8482 (view on Phabricator)
Merge request reports
Activity
heh sorry for the title mess
ok, but i'm a bit confused about the absence of conditional regarding the second hard drive configured. It's what I tried to explained in the comment line 5-6 in kubelet.pp In fact, the second disk must exist for zfs::docker and we just have to use the same datapool. Depending of the vdb location, the write will be done on ceph or local storage. As kubelet is only used in a rancher environment which needs docker, I've limited the refactoring, but you're right it should be more explicit
Please register or sign in to reply