docs: add some complete samples for node_labels and dynamic vars render by inventory group

[kelein]

What type of PR is this?
/kind documentation

What this PR does / why we need it:

1. Add example for node_labels var defination to label or taint nodes
2. Add example for dynamic render containerd_default_runtime var by inventory group
3. Add example for containerd_additional_runtimes of nvidia
4. Add example for dynamic render nvidia_gpu_nodes var by inventory group'
5. Change local_release_dir var with kube_version suffix

Which issue(s) this PR fixes:
NONE

Special notes for your reviewer:

• sample for node_labelsdefination
• sample for dynamic set containerd_default_runtime
• sample for dynamic set nvidia_gpu_nodes var

Does this PR introduce a user-facing change?:

NONE

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: kelein / name: Kallen Ding (5502961, 524fad3, 6170851, 081b40b, 54cd54f, 1ec59f8, 817674b, 66e9f03)

[k8s-ci-robot]

Welcome @kelein!

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 @kelein. 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.

[VannTen]

/ok-to-test
/label ci-short

[VannTen]

This should rather be in as a comment in the default section where node_labels is defined.

[kelein]

I have write a example in docs/ansible/vars.md to describe how to set labels in inventory.ini format, do this way feasible ?

[VannTen]

nvidia_gpu_nodes are a pretty specific usecases, which should not be in the basic example inventory.

[VannTen]

Is there a specific reason for this ? Does not seem needed

[kelein]

I have installed k8s with different version many times which the local release dir stored so many binary files of many version. Just only applies to my scene, I had rollback this change.

[VannTen]

You'll need to remove your merge commit by rebasing as indicated by the CI robot.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kelein

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

Needs approval from an approver in each of these files:

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

[kelein]

You'll need to remove your merge commit by rebasing as indicated by the CI robot.

@VannTen Thanks for your review, I had reopen it in #11806. 🤝

[VannTen]

Please try to avoid closing and reopening new PRs, and rebase your branch when needed instead. Otherwise we lose the history and the context.