Comment 7 for bug 1988119
Revision history for this message
| Lee Van Steerthem (leevs) wrote Re: Update to systemd 237-3ubuntu10.54 broke dns | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
cfa369d
(Get the code!)
Not sure if this is the best place to help people out understanding if nodes are impacted.
We already saw 2 different types of impact on our Azure AKS clusters.
- Pod not able to Terminate
- New images being pulled from ACR (or any container registry
Sometimes it was very clear that we saw the nodes where "Not Ready` in order cases it's very hard to detect.
We have found a way to detect if your nodes are affected.
kubectl logs <pod name>
When you get the following error you know it's impacted: Error from server (InternalError): Internal error occurred: Authorization error (user=masterclient, verb=get, resource=nodes, subresource=proxy)
So restarting the node will help and especially if your cluster is sensitive then you can be more granular about the restart.
I hope it helps some visitors from the azure status page