Promote Improved multi-numa alignment in Topology Manager to beta

[PiotrProkop]

• One-line PR description: Promote Improved multi-numa alignment in Topology Manager to beta

• Issue link: Improved multi-numa alignment in Topology Manager #3545

• Other comments:

[ffromani]

/cc

[ffromani]

Minor: you may want to check the Release Signoff Checklist to see if you can/should check more items.

It seems to me there's a TBD left in the Production Readiness Questionnaire, could you please check?

[PiotrProkop]

Minor: you may want to check the Release Signoff Checklist to see if you can/should check more items.

It seems to me there's a TBD left in the Production Readiness Questionnaire, could you please check?

Thanks for the review. Updated both sections.

[jeremyrickard]

👋 Taking a look at this as a PRR shadow and I had a general question about troubleshooting and operators understanding that the feature is working correctly.

There is a fair bit of detail around how someone can know that it's working by comparing specific workloads but there isn't much detail about cluster operators really understanding this (including with upgrade/downgrade. Could you provide a little more thought/insight from that perspective? Specifically on a rollout, if the kubelet may fail to tart or the kubelet may crash, how do we determine those scenarios are due to this enhancement?

[jeremyrickard]

On Line 372 under the rollout / rollback section, this is mentioned:

Kubelet may fail to start. The kubelet may crash.

Is that statement valid, and if so could we identify what those failure modes might be? How does someone recover from that failure mode?

[PiotrProkop]

Thanks for pointing that out. I think there are only 2 scenarios where kubelet can crash due to this feature:

• bad policy option name, we are already logging appropriate logs for this, to recover one just have to provide correct policy name or disable TopologyManagerPolicyOptions
• cadvisor is not exposing distances for NUMA domains, we are also logging it, to recover one has to disable TopologyManagerPolicyOptions

I'll update KEP with those steps.

[PiotrProkop]

Section updated.

[dchen1107]

/lgtm
/approve

[johnbelamaric]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dchen1107, johnbelamaric, PiotrProkop

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• keps/prod-readiness/OWNERS [johnbelamaric]
• keps/sig-node/OWNERS [dchen1107,johnbelamaric]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment