Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
l
late-needle-80860
03/18/2023, 8:26 PMFeel VERY free to chime in on this discussion > https://github.com/longhorn/longhorn/discussions/5593 < 😄 thank you!
Anyone with a take on this one?
p
polite-piano-74233
03/24/2023, 1:27 AMsome combo of having new worker nodes already online with the new value set, volume cloning https://kubernetes.io/docs/concepts/storage/volume-pvc-datasource/ and all of the manual edits ready to go as kubectl apply -f yaml file writes?
also have REALLY good backups and make sure all your PVs are set to retain before trying
l
late-needle-80860
03/24/2023, 9:21 PMUh yeah. Like the idea. The issue is that for new workers to get the new location of the kubelet. The longhorn workloads I mention in the discussion that I’ve lined to, needs to be updated. When that’s done those are recreated and now the old volumes are no longer able to properly umount the volumes.
@mysterious-boots-59774 if I may. What would be your take on this?
Anyone else with a take on this? Have people seen the discussion I linked to? Would be really happy to get a pointer or two on this.
Thank you very much….
( appreciate you chiming in @polite-piano-74233 thanks )