This message was deleted.
# generala
adamant-kite-43734
03/03/2023, 7:33 PMThis message was deleted.
c
clever-salesmen-35792
03/03/2023, 7:34 PMFor context, our rancher cluster is running on 1.25 (due to an accidental upgrade), which forced us to upgrade to the latest version of rancher and use the RC version.
Now some clusters are working, but there are 2 or 3 that are having the above error.
clever-salesmen-35792
03/03/2023, 8:57 PMWe solved this... Seemed to be firewall issues blocking pot
9443clever-salesmen-35792
03/03/2023, 8:57 PM(and we haven't changed firewall rules)
b
bitter-breakfast-14780
03/06/2023, 2:13 PM@clever-salesmen-35792 we're having the same issue after upgrading to Ubuntu 20.02 - where did you need to make the firewall change and how did you notice the block?
c
clever-salesmen-35792
03/06/2023, 5:19 PMSo running this in all of our clusters helped:
https://suse.com/support/kb/doc/?id=000020699
It was actually changed to the following (found from rancher github)
Copy code
kubectl delete secret -n cattle-system cattle-webhook-tls
kubectl delete <http://mutatingwebhookconfigurations.admissionregistration.k8s.io|mutatingwebhookconfigurations.admissionregistration.k8s.io> --ignore-not-found=true <http://rancher.cattle.io|rancher.cattle.io>
kubectl delete pod -n cattle-system -l app=rancher-webhookb
bitter-breakfast-14780
03/06/2023, 6:11 PMcool i will check that out thank you
bitter-breakfast-14780
03/08/2023, 1:10 PMso my issue was because i had a dummy registries.yaml that i was loading that k3s was trying to read. removing it solved my issue.
766 Views