You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for a recent bad node, this suspiciously reported no internal or external ip for the bad node. We should add the command to our diagnostics when this issue comes up so that we can isolate and remove the problematic node more easily than the past.
The text was updated successfully, but these errors were encountered:
(associated incident report incoming)
With recent versions of GKE, it has become possible for
kubectl logs
to fail with:we should perhaps have a test for this and notify when it's not working.
Additionally, it appears that this is caused by a node with wonky network status:
The following command:
reports addresses of nodes, which normally looks like:
for a recent bad node, this suspiciously reported no internal or external ip for the bad node. We should add the command to our diagnostics when this issue comes up so that we can isolate and remove the problematic node more easily than the past.
The text was updated successfully, but these errors were encountered: