Release tracker for v0.11.0

[mkumatag]

/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 kubernetes/test-infra for CAPIBM jobs
• Bump machine images in CI to use relevent Kubernetes version

[Amulyam24]

@mkumatag, this should be for v1.10.0 right? since these are actions to be done post the release

[mkumatag]

@mkumatag, this should be for v1.10.0 right? since these are actions to be done post the release

This is post release task of v0.10.0 version and prep work for v0.11.0(upcoming CAPIBM release)

[Amulyam24]

• Update Infrastructure Provider version in metadata.yaml and e2e test config files - Post v0.10.0 release housekeeping #2200

• Update release branch versions for weekly security scan - Post v0.10.0 release housekeeping #2200

• Update release support data in docs -Post v0.10.0 release housekeeping #2200

• Update docs with reference to latest release - Post v0.10.0 release housekeeping #2200

• Update and add documentation link for new release branch in Netlify - Add release-0-10 book link #2209

• Add new presubmit job for latest release kubernetes/test-infra for CAPIBM jobs - CAPIBM: add a new presubmit job for release-0.10 and update kubekins-e2e image kubernetes/test-infra#34342

• Bump machine images in CI to use relevent Kubernetes version

[Amulyam24]

/close

[k8s-ci-robot]

@Amulyam24: Closing this issue.

In response to this:

/close

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.