feat(calico): add configurable ipam strictaffinity

[eyenx]

What type of PR is this?

/kind feature

What this PR does / why we need it:
User can now configure IPAM Strictaffinity in case they need it to be enabled. This is needed a.e. for Windows Nodes integration

Which issue(s) this PR fixes:

Fixes #8583

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[Calico] Add configurable ipam strictaffinity (using `calico_ipam_strictaffinity` param)

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Toni Tauro (c203ffd)

[k8s-ci-robot]

Welcome @eyenx!

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

[cristicalin]

From what I can tell this approach will only enable strict affinity, if a deployer later decides to disable strict affinity this will not help. If so, why does this need to be part of the deployment process if it can be easily enabled via calicoctl later on? Ideally the deployment tool should configure parameters that end up in configuration files that are later more difficult to change.

[eyenx]

You are totally right @cristicalin I'm changing this so that it will enable or disable (defualt) the strictaffinity accordingly

[eyenx]

a26d80d

[cristicalin]

@eyenx please squash the commits into a single one to keep the history clean, then we can merge this change.

[eyenx]

@cristicalin done.

[floryut]

@eyenx Thank you
/ok-to-test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eyenx, floryut

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 [floryut]

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

[cristicalin]

/lgtm