Prepare for release v1.9 minor release

[mquhuy]

Here we can track the tasks related to release 1.9

Tasks

• Prepare dev-env to acommodate new release related changes and configurations. Prior art: 1, 2
  • PR: add support for release-1.9 metal3-dev-env#1485
• Release Ironic, also check new image is created in quay. Prior art: v26.0.0 release
• Pin Ironic in BMO. Prior art
• Pin Ironic in metal3-dev-env. Prior art
• Uplift CAPI to v1.9.0 in IPAM and CAPM3, also check migration guide: Migration guide for providers . Prior art IPAM, Prior art CAPM3
• Uplift k8s to 1.32 in CAPM3 repo. Prior art
  • PR: 🌱 Bump k8s to v.1.32.0 and CAPI to v1.9.1 #2158
• Uplift k8s to 1.32 in metal3-dev-env repo. Prior art
  • PR: 🌱 Bump k8s to 1.32.0 metal3-dev-env#1484
• Uplift k8s to 1.32 in image building pipeline. Prior art: 1, 2
  • PR: 🌱 Bump k8s to 1.32.0, crictl to 1.32.0 and crio to 1.31.3 project-infra#929
• Release IPAM (Make release note PR, also check new image is created in quay).
  • https://github.com/metal3-io/ip-address-manager/releases/tag/v1.9.1
• 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
  • https://github.com/metal3-io/baremetal-operator/releases/tag/v0.9.0
• Bump IPAM and BMO in CAPM3 in main Prior art
  • PR: https://github.com/metal3-io/metal3-dev-env/pull/2170
• Release CAPM3 (Branch out, add branch protection and required tests, also check new image is created in quay).
  • https://github.com/metal3-io/cluster-api-provider-metal3/releases/tag/v1.9.0
• Add/edit JJBs to accommodate new build jobs and PR jobs for new release branches. And remove unsupported releases tests for CAPM3 and IPAM. Prior art
  • PR adding 1.9 jobs: https://gerrit.nordix.org/c/infra/cicd/+/22800
  • PR removing 1.6 jobs: https://gerrit.nordix.org/c/infra/cicd/+/22802
• Add Prow jobs for new release branches in Project-infra repo, also remove unsupported releases tests for CAPM3 and IPAM here too Prior art
  • PR IPAM: add IPAM 1.9 release to Prow project-infra#931
  • PR BMO: add BMO release-0.9 to Prow project-infra#933
  • PR CAPM3: add CAPM3 release-1.9 to Prow project-infra#934
  • PR remove 1.6 tests: remove untested branches (1.6 series) from Prow project-infra#935
  • PR add triggers to other repos: add release-1.9 triggers to other repos project-infra#936
• Check CI if new releases are tested properly or not
• Update CAPM3 README.md with the new e2e triggers, on both the release-1.9 and on main. Prior art: 1, 2
  • PR main: 📖 Updating docs for release 1.9 #2232
  • PR release-1.9: 📖 update build badges and triggers in README.md #2185
• Update IPAM README.md with the new e2e triggers, on both the release-1.9 and on main. Prior art: 1, 2
  • PR release-1.9: 📖 update build badges for release-1.9 ip-address-manager#813
• Update BMO README.md with the new e2e triggers, on both the release-0.9 (if applicable) and on main. Prior art: 1, 2
  • PR main: 🌱 Add release 0.9 e2e tests and branch release-0.9 to README baremetal-operator#2134
  • PR release-0.9: 🌱 Update README badges and e2e triggers baremetal-operator#2175
• Add BMO upgrade test for release-0.9 -> main, and update all ironic upgrade tests to use release-0.9, also remove tests for release-0.5 Prior art
  • PR: 🌱 Add release 0.9 e2e tests and branch release-0.9 to README baremetal-operator#2134
• Update Metal3 book. Prior art: 1, 2
  • PR: update version support tables for release-1.9 metal3-docs#491
• Announce the releases

Post-release tasks

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

• Add CAPI v1.9 contract. Prior art
  • PR: 🌱 add support for 1.10 in e2e #2164
• Update clusterctl tests to accommodate new releases. Prior Art
  • PR: 🌱 add support for 1.10 in e2e #2164
  • PR: 🌱 Update clusterctl tests for 1.9 #2242

[Rozzii]

/triage accepted
/kind ci dependency

[metal3-io-bot]

@Rozzii: The label(s) kind/dependency cannot be applied, because the repository doesn't have them.

In response to this:

/triage accepted
/kind ci dependency

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.

[tuminoid]

CI prepping PRs: JJB, Prow, contracts, dev-env etc:

• https://gerrit.nordix.org/c/infra/cicd/+/22800
• https://gerrit.nordix.org/c/infra/cicd/+/22802
• add IPAM 1.9 release to Prow project-infra#931
• add support for release-1.9 metal3-dev-env#1485
• add BMO release-0.9 to Prow project-infra#933
• add CAPM3 release-1.9 to Prow project-infra#934
• remove untested branches (1.6 series) from Prow project-infra#935
• update version support tables for release-1.9 metal3-docs#491
• add release-1.9 triggers to other repos project-infra#936
• 🌱 add support for 1.10 in e2e #2164
• 🌱 update dependabot config for release-0.9 baremetal-operator#2135
• 🌱 update dependabot config for release-1.9 #2165
• update branches to sync Nordix/metal3-dev-tools#778

[kashifest]

whats left here @adilGhaffarDev @mquhuy @peppi-lotta

[peppi-lotta]

whats left here @adilGhaffarDev @mquhuy @peppi-lotta

The task list is up to date: only one PR is waiting to be merged and then everything is done.

[kashifest]

The task list is up to date: only one PR is waiting to be merged and then everything is done.

I think we have announced the release, so we can tick that as well.