Rancher - Rancher UI Webpage 504 Gateway Time-out скачать в хорошем качестве

Rancher - Rancher UI Webpage 504 Gateway Time-out

Discover how to resolve Rancher 504 gateway time-out issue. Here are the commands outlined my video. Check the Rancher service and ingress kubectl get svc,ingress -n cattle-system kubectl describe ingress rancher -n cattle-system Check NGINX ingress pods kubectl get pods -A -o wide | grep -i nginx Check Rancher pod status and logs kubectl get pods -n cattle-system -o wide kubectl describe pods -n cattle-system -l app=rancher Health check commands first to see if the pods are actually responding internally --------------------------------------------------------------------------------- Test each Rancher pod's health endpoint kubectl exec -n cattle-system rancher-86984c6d89-cmlcv -- curl -s -o /dev/null -w "%{http_code}" http://localhost:80/healthz kubectl exec -n cattle-system rancher-86984c6d89-dmvsg -- curl -s -o /dev/null -w "%{http_code}" http://localhost:80/healthz kubectl exec -n cattle-system rancher-86984c6d89-pm9sl -- curl -s -o /dev/null -w "%{http_code}" http://localhost:80/healthz Check response with timing (should complete within 5 seconds) #200 status code = HTTP success (healthy) kubectl exec -n cattle-system rancher-86984c6d89-cmlcv -- timeout 5 curl -v http://localhost:80/healthz kubectl exec -n cattle-system rancher-86984c6d89-dmvsg -- timeout 5 curl -v http://localhost:80/healthz kubectl exec -n cattle-system rancher-86984c6d89-pm9sl -- timeout 5 curl -v http://localhost:80/healthz Test the main Rancher API endpoint kubectl exec -n cattle-system rancher-86984c6d89-cmlcv -- curl -s http://localhost:80/v3 kubectl exec -n cattle-system rancher-86984c6d89-dmvsg -- curl -s http://localhost:80/v3 kubectl exec -n cattle-system rancher-86984c6d89-pm9sl -- curl -s http://localhost:80/v3 Get recent logs from each pod kubectl logs -n cattle-system rancher-86984c6d89-cmlcv --tail=10 kubectl logs -n cattle-system rancher-86984c6d89-dmvsg --tail=10 kubectl logs -n cattle-system rancher-86984c6d89-pm9sl --tail=10 Check memory and CPU usage inside the containers kubectl exec -n cattle-system rancher-86984c6d89-cmlcv -- top kubectl exec -n cattle-system rancher-86984c6d89-dmvsg -- top kubectl exec -n cattle-system rancher-86984c6d89-pm9sl -- top Test if pods can reach each other kubectl exec -n cattle-system rancher-86984c6d89-cmlcv -- ping -c 3 10.42.1.137 kubectl exec -n cattle-system rancher-86984c6d89-cmlcv -- ping -c 3 10.42.3.35 ◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇ Restart "canal" pods -------------------- Restart the Canal pods, use: kubectl delete pods -n kube-system -l k8s-app=canal Watch Calico pods restart in kubectl get pods -n kube-system -l k8s-app=canal ◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇ Restart "rancher" pods ---------------------- kubectl get pods -A -o wide | grep -E "(rancher.*)" Since the pods are running but unhealthy, let's restart the deployment Restart the problematic pods: kubectl delete pod -n cattle-system rancher-86984c6d89-cmlcv rancher-86984c6d89-pm9sl kubectl delete pod -n cattle-system rancher-86984c6d89-7vc65 OR---- Restart the Rancher deployment kubectl rollout restart deployment rancher -n cattle-system Monitor the new pods kubectl get pods -n cattle-system -l app=rancher -w ◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇ Key Commands ------------ Restart the Canal pods, use: kubectl delete pods -n kube-system -l k8s-app=canal Watch Calico pods restart in kubectl get pods -n kube-system -l k8s-app=canal Restart the problematic pods: kubectl delete pod -n cattle-system rancher-86984c6d89-cmlcv rancher-86984c6d89-pm9sl OR---- Restart the Rancher deployment kubectl rollout restart deployment rancher -n cattle-system Monitor the new pods kubectl get pods -n cattle-system -l app=rancher -w #Setup Kubectl EWnvironment variables and symbolic link sudo ln -s /var/lib/rancher/rke2/bin/kubectl /usr/local/bin/kubectl export KUBECONFIG=/etc/rancher/rke2/rke2.yaml ◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇◇◆◇◆◇◆◇ #kubernetes #fypシ #github #rke2