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

add anti-affinity to ensure modsec and default ingress controllers aren't placed on the same node #6567

Open
jaskaransarkaria opened this issue Dec 12, 2024 · 0 comments

Comments

@jaskaransarkaria
Copy link
Contributor

Background

ingress-controllers                                   nginx-ingress-default-controller-6b6fd6b654-bpqnb                ●  1/1   Running                            0 1685 3407   1685    n/a     66     16 172.20 │
│ ingress-controllers                                   nginx-ingress-modsec-controller-9b74d6b46-4vpjn                  ●  3/3   Running                            0 1312 4241    656    n/a     92    n/a 172.20

We are seeing CPU spikes when ingress controllers are placed on the same node

add anti-affinity to ensure they are placed on separate nodes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

2 participants