Calico: update files to handle multi-asn bgp peering conditions.

[catblade]

What type of PR is this?
/kind bug

What this PR does / why we need it:
Without these changes, multi-ASN configs will not work.

• Add in ability for kubespray to configure ASNs according to routers being peered with by the node instead of relying on the user to put in local_as for every single node.
• Add in option to have BGP configured so that we can choose to not have a global ASN. With multiple ASNs, will not work.

Tested on our little cluster with a switch. Do not see infrastructure in kubepsray proper to test this type of config (needs switch configuration to test). We have an iperf test that works with these changes.

Which issue(s) this PR fixes:

Fixes #
#6845

Special notes for your reviewer:
You may wish to talk to me directly in how to set a switch for testing.

Does this PR introduce a user-facing change?
Yes.

New item in samples shows you can choose not to set a global calico ASN, option named calico_no_global_as_num
No longer need to set local_as per-node. It will pull it in from the tors as they are defined by node. This will make changing servers between racks (or otherwise configuring) less prone to user error.

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

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. I understand the commands that are listed here.

[k8s-ci-robot]

Hi @catblade. 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.

[catblade]

@mirwan

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: catblade, mirwan

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

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

[mirwan]

/ok-to-test

[mirwan]

/lgtm