-
Notifications
You must be signed in to change notification settings - Fork 25
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
balloons: expose balloons and optionally containers with affinity in NRT #469
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work @askervin !
One question, I just ran a test from your branch and in my bare minimum cluster where there isn't any real workload with hundreds of Pods, the size of the NRT object was close to 600 lines. I'm just wondering if you have verified that if there is any limit from the api-machinery for the size of the CRD. Because in case of production level cluster, there might be hundreds of pods running and size of the NRT will grow quite fast as every container has its own zone attribute.
Would you mind to share why did you mean (optionally) on the PR title? |
When enabled, the balloons policy exposes containers in balloons as node resource topology subzones. This enables inspecting, for instance, CPU and memory affinity of any ballooned containers via node resource topology customer resources. Signed-off-by: Antti Kervinen <[email protected]>
72856f0
to
8b45f84
Compare
Signed-off-by: Antti Kervinen <[email protected]>
Signed-off-by: Antti Kervinen <[email protected]>
Signed-off-by: Antti Kervinen <[email protected]>
8b45f84
to
23df214
Compare
|
No description provided.