Harshal Patil
Harshal Patil
/retest-required
I have observed this happening only on cgroup v2 systems.
/close as it seems the bug was in the kubelet code.
I was wondering instead of using `Conditions` directly, should have something like `NodeConditions` (like we [tried this once with workerLatencyProfiles](https://github.com/openshift/api/pull/1187/files#diff-7ffc4ab9c9775f324fe2d76ccd536e7a646e95fe8561ef91c5f519826d6a8411L47))? /cc @deads2k @rphillips
In case of worker latency profiles, we thought of adding a latency profile specific status in `NodeStatus`. Since nodes.config object deals with various node related features, I thought maybe if...
> if we have a cgroup specific one, then we'd probably deprecate the field when cgroupv1 was finally dropped This will unlikely to get deprecated. Not sure why would we...
@rphillips OCP is deprecating cgroup v1 support, upstream k8s is just going to keep it in maintenance mode. This PR is to allow us display deprecation notice if the OCP...
> /cc @harche @haircommander @mrunalp I tried to include some comparisons and community updates here. But this is still a draft somehow. I would like to make it late 2024....
> * [@HirazawaUi](https://github.com/HirazawaUi) and [@hshiina](https://github.com/hshiina) have some working PRs. That's correct, the promising fixes are coming from @HirazawaUi and @hshiina. Waiting on this for now on that PR https://github.com/kubernetes/kubernetes/pull/129355#issuecomment-2644427236