fix: Enable NRI for containerd and disable plugin when nri_enabled is false

[ShinyaIshitobi]

What type of PR is this?
/kind bug

What this PR does / why we need it:

This PR updates the nri_enabled configuration in Kubespray to:

• Automatically enable the Node Resource Interface (NRI) plugin when container_manager == 'containerd'
• Disable the NRI plugin (and fully deactivate it per Containerd documentation) for all other container runtimes (e.g., CRI-O)

Which issue(s) this PR fixes:

Fixes #12118

Special notes for your reviewer:

This is my first open-source contribution, so there may be areas that need improvement; thank you in advance for your review.

Does this PR introduce a user-facing change?:

Enable NRI by default on containerd (following containerd defaults)

[k8s-ci-robot]

Welcome @ShinyaIshitobi!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @ShinyaIshitobi. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[tico88612]

/kind bug
/ok-to-test

[tico88612]

/lgtm

Thank you!

[ShinyaIshitobi]

/assign

[ShinyaIshitobi]

/assign VannTen

[yankay]

Thanks @ShinyaIshitobi
/lgtm

[tico88612]

/retest-failed

[VannTen]

To check my understanding: this is about following upstream defaults, right ?

NRI is enabled on containerd but not on CRI-O ?

IMO even if it's upstream, it warrants a release.

[tico88612]

Yes, this is following containerd upstream, and make sure nri_enabled is work.

CRI-O's NRI default is still disabled.

[VannTen]

Ok, thanks /approve /release-note-edit ```release-note Enable NRI by default on containerd (following containerd defaults) ```

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ShinyaIshitobi, tico88612, VannTen

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:

• OWNERS [VannTen]

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