Folks, I ran: ```kubectl delete daemonset rke2-in...
# general
b
Folks, I ran:
Copy code
kubectl delete daemonset rke2-ingress-nginx-controller -n kube-system
It's gone and now I want to get the ingress-nginx-controller back and it's becoming tough. I thought applying
/var/lib/rancher/rke2/server/manifests/rke2-ingress-nginx.yaml
would help, but no. Re-starting
rke2-server
with the thought that it'll re-deploy it, doesn't work either. What can I try next?
c
Why did you do that?
You need to update chart values to trigger an update to the helm chart so that it redeploys it.
In the future, if you don't want something, disable it instead of just deleting it
1
b
The ingress container was failing continuously due this error:
Copy code
plugin type="calico" failed (add): failed to allocate for range 0: no IP addresses available in range set: 10.42.5.1-10.42.5.254
I thought I would delete it and then re-create, only to find it's not straight-forward.
c
You can delete pods and they'll come right back if they're part of a deployment or daemonset or so on . If you delete the deployment itself... you're gonna have to take manual steps to get it back.
1
p
cilium released version 1.18.0 around a week ago with a ton of improvements, how fast will the new version get pulled into rancher rke2 releases?
c
Might make it for August, might not. https://github.com/rancher/rke2-charts/pull/749
👀 1