Configuring PodNodeSelector via variables

[titansmc]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test

/kind feature

/kind flake

What this PR does / why we need it:
Allows the users to configure the the clusterDefaultNodeSelector from the config file
Which issue(s) this PR fixes:

Fixes #10412

Special notes for your reviewer:
closing #10509 10509

This will introduce a new variable `kube_apiserver_admission_plugins_podnodeselector_default_node_selector`  that can be used with `kube_apiserver_admission_plugins_needs_configuration: [PodNodeSelector]` defined. So allows the users to configure PodNodeSelector plugin.

[linux-foundation-easycla]

• ✅ login: titansmc / name: jandres - moscardo (44fdf16, 8c56f8c, ac6475e, bf798e8, bb4175b, 1af2d3a, 6211a6d, 79f6a8b, 48f506e, 67b6f53)
• ❌ The email address for the commit (75a6035) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

Hi @titansmc. 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/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: titansmc
Once this PR has been reviewed and has the lgtm label, please assign floryut for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[titansmc]

Hi, It is a bit annoying that I cannot continue....It seems that the PR itself (when I do it via web interface) is not recognize as my user, look the last entry as it is not like the others:

if we cannot fix this, can someone take those changes and make their own PR ?

[floryut]

Hi, It is a bit annoying that I cannot continue....It seems that the PR itself (when I do it via web interface) is not recognize as my user, look the last entry as it is not like the others:

if we cannot fix this, can someone take those changes and make their own PR ?

You don't have access to a git cli somehow ? you only need to rebase your changes

[titansmc]

I use the github web interface to create a PR from a forked branch
What do you mean to rebase the changes ?

[titansmc]

I am doing everything command line, but the final PR request I do it via github.com , and this PR is also considered a commit and it is where the License agreement fails.

[yankay]

/ok-to-test

[titansmc]

/easycla

[titansmc]

it passed the CLA on #10607 @yankay