🌱 E2E: Update Calico to v3.30.2

[lentzi90]

What this PR does / why we need it:

This updates Calico that we use in the e2e tests.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged): Fixes #2566

Special notes for your reviewer:

1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

• [x] squashed commits
• if necessary:
  • [ ] includes documentation
  • [ ] adds unit tests

[netlify[bot]]

✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!

Name	Link
🔨 Latest commit	1872dc4050e4abb983e2e284736e3909420249c2
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-cluster-api-openstack/deploys/685b9974557eba0008f6bb07
😎 Deploy Preview	https://deploy-preview-2609--kubernetes-sigs-cluster-api-openstack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[lentzi90]

/test pull-cluster-api-provider-openstack-e2e-full-test

[lentzi90]

/cc @mdbooth @EmilienM I know this looks like a lot of lines changed, but it is just copying the latest calico manifest from upstream. The manifest we use in e2e currently is ~3 years old :grimacing:

[mdbooth]

/approve /lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mdbooth

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~~ [mdbooth]

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

[lentzi90]

/cherry-pick release-0.12 release-0.11

[k8s-infra-cherrypick-robot]

@lentzi90: new pull request created: #2642

In response to this:

/cherry-pick release-0.12 release-0.11

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.