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

IstioD is using too many resources when lots of pods are being added/churned #2332

Closed
RobertLucian opened this issue Jul 12, 2021 · 0 comments · Fixed by #2342
Closed

IstioD is using too many resources when lots of pods are being added/churned #2332

RobertLucian opened this issue Jul 12, 2021 · 0 comments · Fixed by #2342
Assignees
Labels
bug Something isn't working performance A performance improvement
Milestone

Comments

@RobertLucian
Copy link
Member

Description

Find a way to disable the monitoring of k8s resources so that istiod stops using so many resources.

Consequence

When istiod uses too much memory, it triggers an OOM event on the other pods collocated on the same instance such as the ingress gateways, the cluster autoscaler, the operator, etc. Or it can make k8s evict the other pods which is equally bad. This can render the cluster unusable.

@RobertLucian RobertLucian added the bug Something isn't working label Jul 12, 2021
@RobertLucian RobertLucian self-assigned this Jul 12, 2021
@RobertLucian RobertLucian added the performance A performance improvement label Jul 15, 2021
@deliahu deliahu added this to the v0.39 milestone Jul 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working performance A performance improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants