Cni toleration for tainted nodes

[jhohertz]

Related to #5730, replaces #5802 (mistakenly issued against release-1.10 branch)

This increases the tolerations for the two CNIs in the subject to allow them to deploy/work on clusters with instance groups that have a taint to them.

Note: I've not been able to test this in a build due to other apparent issues in the build (I am new to this codebase), but have verified that patching these manifests after the fact addresses the stated issue.

As mentioned in the other ticket, this is very similar changes made for other CNI providers as follows:

Canal: #3802, #3142
Calico: #3097

[chrisz100]

/ok-to-test

[chrisz100]

/lgtm
/assign @mikesplain
/assign @justinsb

Thank you for fixing this!

[mikesplain]

Thanks so much for this @jhohertz! For these changes to get picked up, you'll have to bump the version here as well:

kops/upup/pkg/fi/cloudup/bootstrapchannelbuilder.go

Line 743 in 3f6df6f

version := "1.0.0-kops.1"

(bump the .1 to .2) and also bump for cilium as well in the same manor. Thanks!

[mikesplain]

Perfect, thanks @jhohertz!

/lgtm
/approve

[mikesplain]

Oops, looks like you'll have to update the test as well:

kops/upup/pkg/fi/cloudup/tests/bootstrapchannelbuilder/cilium/manifest.yaml

Line 72 in 6f1874a

version: v1.0-kops.1

[jhohertz]

Thanks for helping me through this first PR. :)

[chrisz100]

No worries! A pleasure :-)
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrisz100, jhohertz, mikesplain

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

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

[mikesplain]

/retest