Channels
extensions
rancher-extensions
supermicro-sixsq
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
onlinetraining
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
random
elemental
espanol
lima
harvester-dev
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
neuvector-security
rancher-setup
developer
office-hours
mexico
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
rke2
s3gw
hobbyfarm
rancher-desktop
general
Title
a
ambitious-plastic-3551
06/30/2022, 7:18 PMI find this interesting... I have 3 nodes, I disabled rke2-ingress-nginx on two nodes, but when I restart one node, they either kill all nginx processes, or have all of them đ
f
fierce-summer-6167
06/30/2022, 7:23 PMHow did you disable rke2-ingress-nginx?
c
creamy-pencil-82913
06/30/2022, 10:39 PMyou shouldnât disable a packaged component on one server in the cluster while leaving it enabled on the others. The one that still has it enabled will re-deploy the chart to the cluster whenever you restart it.
disabled components should be in sync across all servers.
a
ambitious-plastic-3551
07/01/2022, 3:58 AMFound out the hard way