Release tracker for v0.12.0

[Prajyot-Parab]

/area provider/ibmcloud

Tasks:

After every CAPIBM major version release:

• Update Infrastructure Provider version in metadata.yaml and e2e test config files
• Update release branch versions for weekly security scan
• Update release support data in docs
• Update docs with reference to latest release
• Update and add documentation link for new release branch in Netlify
• Add new presubmit job for latest release branch in kubernetes/test-infra
  • Update kubekins-e2e image to relevent Kubernetes version
• Add E2E CI jobs for latest release branch in ppc64le-cloud/test-infra
  • Bump machine images in CI to relevent Kubernetes version
  • Update kubekins-e2e image to relevent Kubernetes version

Note:

1. An example for infrastructure provider version upgrade, if we cut a release for version
   0.9.0, update the infratructure provider version to 0.10.0 on the main branch.
2. Keep the version upgrades in check for the main branch and the two latest releases.

[Amulyam24]

• Add new presubmit job for latest release branch in kubernetes/test-infra - Add presubmit jobs for CAPIBM release-0.11 branch kubernetes/test-infra#34803

  • Update kubekins-e2e image to relevent Kubernetes version

• Add E2E CI jobs for latest release branch in ppc64le-cloud/test-infra - Update CAPIBM kubekins image and E2E jobs to test release version 0.11.0 ppc64le-cloud/test-infra#556

• Bump machine images in CI to relevent Kubernetes version - waiting for 1.32 image to be created and tested

• Update kubekins-e2e image to relevent Kubernetes version - Update CAPIBM kubekins image and E2E jobs to test release version 0.11.0 ppc64le-cloud/test-infra#556

[Prajyot-Parab]

@Amulyam24 anything pending here?

[Amulyam24]

VPC machine image update to 1.32 in CI is pending.