Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TestAccNetworkPolicies flake #1465

Open
flostadler opened this issue Oct 28, 2024 · 1 comment
Open

TestAccNetworkPolicies flake #1465

flostadler opened this issue Oct 28, 2024 · 1 comment
Labels
impact/flaky-test A test that is unreliable kind/engineering Work that is not visible to an external user

Comments

@flostadler
Copy link
Contributor

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.

@flostadler flostadler added impact/flaky-test A test that is unreliable kind/engineering Work that is not visible to an external user labels Oct 28, 2024
@flostadler flostadler self-assigned this Oct 28, 2024
@flostadler flostadler removed their assignment Nov 11, 2024
@flostadler
Copy link
Contributor Author

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/flaky-test A test that is unreliable kind/engineering Work that is not visible to an external user
Projects
None yet
Development

No branches or pull requests

1 participant