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
It's failing because one of the two coredns pods isn't ready: 6 out of 7 Pods are ready.
The coredns container of that pod seems to be restarting, I saw this in the logs: "restartCount": 4
I'm gonna dig a bit deeper if coredns needs some special configuration for network policies. It might be that we need to add some additional network policies for coredns to be allowed to properly communicate.
The text was updated successfully, but these errors were encountered:
I'm starting to have a suspicion that we might be loading the account with too many clusters and nodes at once. Will do some digging if I can find out whether we're running into any limits (e.g. EC2 instance limits)
TestAccNetworkPolicies
is flaky.It's failing because one of the two coredns pods isn't ready:
6 out of 7 Pods are ready
.The coredns container of that pod seems to be restarting, I saw this in the logs:
"restartCount": 4
I'm gonna dig a bit deeper if coredns needs some special configuration for network policies. It might be that we need to add some additional network policies for coredns to be allowed to properly communicate.
The text was updated successfully, but these errors were encountered: