WIP: Prepare for release v1.12 of CAPM3, IPAM and 0.12 of BMO

[Sunnatillo]

Here we can track the tasks related to release 1.11 of CAPM3 and IPAM, and release 0.11 BMO
For Ref 1.11 tracker : metal3-io/cluster-api-provider-metal3#2275

Tasks

Releases and Uplifts

• Release Ironic, also check new image is created in quay. Prior art: v26.0.0 release, 27.0.0 release
• Uplift CAPI to v1.12.0 in IPAM and CAPM3, also check migration guide: Migration guide for providers . Prior art IPAM, Prior art CAPM3, Prior infra
  • CAPM3 PR:
  • IPAM PR:
  • BMO PR:
• Uplift k8s to 1.35. in CAPM3 repo. 1, 2, 3, 4
  • PR:
• Uplift k8s to 1.35 in metal3-dev-env repo. Prior art
  • PR:
• Uplift k8s to 1.35 in image building pipeline. Prior art: 1, 2
  • PR:
  • PR:
• Release IPAM (Make release note PR, also check new image is created in quay).
• Check if BMO needs release. If so, release BMO (Branch out, add branch protection and required tests, also check new image is created in quay). Prior art
• Pin Ironic in new release branch in BMO. Make patch release of BMO
  • release-0.12
• Bump IPAM and BMO in CAPM3 in main
  • Prior art
  • release-1.11/0.11 IPAM, BMO
• Release CAPM3 (Branch out, add branch protection and required tests, also check new image is created in quay).e2e prior art

Tests and configs

• Add 1.12 to IPAM metadata.yaml in main. Prior Art
  • Fixing incorrect contract version CAPM3 main, CAPM3 release-1.11
  • release-1.11 Bump
• Update dependabot configs.
  • release-1.10/0.10 CAPM3, IPAM, BMO
  • release-1.11/0.11 BMO, IPAM, CAPM3
• Add/edit JJBs to accommodate new build jobs and PR jobs for new release branches. And remove unsupported releases tests for CAPM3 and IPAM.
  • release-1.12/0.12. Prior art.
  • [release-1.11/0.11]
  • release-1.10/0.10
  • Removing old jobs. Pripr art.
• Add Prow jobs for new release branches in Project-infra repo, also remove unsupported releases tests for CAPM3 and IPAM here too Prior art
  • 1.9/0.9 release IPAM, BMO, CAPM3, MISC
  • 1.10/0.10 release IPAM, PR, PCAPM3, PR remove 1.7 tests, MISC
  • 1.11/0.11 release CAPM3, BMO, IPAM, MISC
• Run /test metal3-centos-e2e-integration-test-release-1-11 metal3-ubuntu-e2e-integration-test-release-1-11 on a PRs opened to the new release branches. Have someone with sufficient rights add mandatory tests as branch protection rules
• Add BMO upgrade test for release-0.11 -> main, and update all ironic upgrade tests to use release-0.11, also remove tests for release-0.9
  • release-0.9,
  • release-0.10,
  • release-0.11
• Check CI if new releases are tested properly or not

Docs

• Update CAPM3 README.md with the new e2e triggers, on both the release-1.11 and on main.
• Prior art: 1, 2
• release-1.11,main - part of prepartion for next cycle
• Update IPAM README.md with the new e2e triggers, on both the release-1.11 and on main.
• Prior art: 1, 2 3
• release-1.11, main
• Update BMO README.md with the new e2e triggers, on both the release-0.11 (if applicable) and on main.
• Prior art: 1, 2
• release-1.11, main
• Update Metal3 book.
• Prior art: 1, 2, 3
• Release 1.11
• Announce the releases

Post-release tasks

Do the following on the main branch after the release is done.

• Add CAPI v1.12 contract.

• Prior art 1, 2

• release-1.11 - part of preparation for new cycle

• Prepare dev-env to acommodate new release related changes and configurations.

• cycle 1.8/0.8: 1, 2

• cycle 1.9/0.9 3,

• cycle 1.10/0.10 4, 5

• cycle 1.11/0.11 6

• Update clusterctl tests to accommodate new releases.

• prior art 1, 2, 3

• release-1.11

• Update dev-env templates after release (prior art)

• release-1.11

[Rozzii]

/triage accepted