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

Kubernetes - Cluster max memory/cpu #237

Open
moshloop opened this issue Jul 19, 2024 · 1 comment
Open

Kubernetes - Cluster max memory/cpu #237

moshloop opened this issue Jul 19, 2024 · 1 comment
Assignees

Comments

@moshloop
Copy link
Member

No description provided.

@yashmehrotra
Copy link
Member

@moshloop

Pretty hard to do this since there would be different lookups for usage and max, since pods and nodes are created dynamically, we can merge the properties with max coming from pod object and value coming from a check

I remember we thought of doing this: flanksource/canary-checker#1378 to solve these kind of scenarios

Is there any other way we can approach this ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants