balloons: expose balloons and optionally containers with affinity in NRT #469
Conversation
There was a problem hiding this comment.
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? |
askervin
force-pushed
the
5Z8_balloons_nrt
branch
from
72856f0 to
8b45f84
Compare
askervin
changed the title
askervin
force-pushed
the
5Z8_balloons_nrt
branch
from
8b45f84 to
23df214
Compare
|
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 <antti.kervinen@intel.com>
Signed-off-by: Antti Kervinen <antti.kervinen@intel.com>
Signed-off-by: Antti Kervinen <antti.kervinen@intel.com>
Signed-off-by: Antti Kervinen <antti.kervinen@intel.com>
askervin
force-pushed
the
5Z8_balloons_nrt
branch
from
23df214 to
88706f3
Compare
|
LGTM. It might be good to have |
No description provided.