https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
c
This doesn't appear to be related to rke2. Is the rancher webhook service running in the local cluster?
s
No it is not running , not even the rancher pod is running
The above ss is for the rancher pod
and this one is for the webhook
when i am trying to create a webhook it says
c
if the rancher pod isn’t running, how are you using the UI?
Are you sure you’re looking in the local cluster?
s
yes one of it was running i i had 3 replica sets
but webhook is causing problems
c
they should all be running
are health checks failing? why does the service have no endpoints?
s
well in the recent events of webhook ( stuck in creating container ) i am seeing this
c
looks like kube-proxy might not be running on that node?
s
letme check and due to this local webhook error i am seeing this on all the downstream cluster
@creamy-pencil-82913 the kube proxy is running but i can see the calico daemon set is showing error
Hey brandon , I fixed it you were right so the kube proxy was in running state ( blue ) but not showing any logs and so i think it was not properly running which was causing the calico pods to fail on those particular nodes and because of calico the webhook was not getting deployed as it was getting scheduled on the same node . So i restarted the rke2-agent on my worker nodes. and kubeproxy and calico started running which inturn enabled all the application workload to success but there is one issue even though every thing is working but on one of the worker node i can kubeproxy not showing any logs even after the agent restart . What can be the reason according to you?
Open in Slack
PreviousNext
Powered by