Describe the migration from systemd's cgroup v1 CPU shares to v2 CPU weight formula

[SergeyKanzhelev]

This is a Feature Request

Docs needs to be added to explain the change in CPU shares weight calculation for cgroupv2.

• when the change happened
• dependant components that are responsible
• how to make sure k8s is aligned with runc on this calculation
• any sideeffects
• what effect it has on older k8s versions

What would you like to be added

See kubernetes/enhancements#5246 (comment)

/sig node
/milestone v1.35
/cc @haircommander @iholder101

Why is this needed

Comments
This change should not affect regular users, but may need explanation for cluster administrators. We will need to link relnotes for 1.35 to this documentation. Theoretically is can affect already released versions as well, but we will mention it in 1.35 notes.

[k8s-ci-robot]

@SergeyKanzhelev: You must be a member of the kubernetes/website-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Website milestone maintainers and have them propose you as an additional delegate for this responsibility.

In response to this:

This is a Feature Request

Docs needs to be added to explain the change in CPU shares weight calculation for cgroupv2.

• when the change happened
• dependant components that are responsible
• how to make sure k8s is aligned with runc on this calculation
• any sideeffects
• what effect it has on older k8s versions

What would you like to be added

See kubernetes/enhancements#5246 (comment)

/sig node
/milestone v1.35
/cc @haircommander @iholder101

Why is this needed

Comments
This change should not affect regular users, but may need explanation for cluster administrators. We will need to link relnotes for 1.35 to this documentation. Theoretically is can affect already released versions as well, but we will mention it in 1.35 notes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[iholder101]

Thanks for opening this @SergeyKanzhelev!

I'd be happy to get it done.
/assign @iholder101