Prepare for release v1.10 minor release

[Rozzii]

Here we can track the tasks related to release 1.10
For 1.9 tracker : #2137

Tasks

• Prepare dev-env to acommodate new release related changes and configurations. Prior art: 1, 2, 3
  • PR: 🌱 Add Support for release-1.10 metal3-dev-env#1523
  • PR: 🌱 Fix source branches of other repos for CAPM3RELEASEBRANCH release-1.10 metal3-dev-env#1529 (fix)

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.10.0 in IPAM and CAPM3, also check migration guide: Migration guide for providers . Prior art IPAM, Prior art CAPM3, Prior infra
• Uplift k8s to 1.33? in CAPM3 repo. Prior art
  • PR: 🌱 Bump Kubernetes to v1.33.0 #2523
  • e2e: 🌱 Change Kubernetes version in e2e tests #2534
  • envtest: 🌱 Uplift Kubernetes to 1.33 in envtest #2535
• Uplift k8s to 1.33 in metal3-dev-env repo. Prior art
  • PR: Bump Kubernetes to 1.33.0 metal3-dev-env#1524
• Uplift k8s to 1.33 in image building pipeline. Prior art: 1, 2
  • Project-infra PR: 🌱 Uplift Kubernetes version to v1.33.0 for image building project-infra#995
  • Project-infra PR: 🌱 Changing mandatory tests for metal3-dev-env and adding 1.9,1.10 for project-infra project-infra#1010 (fix)
  • jjb PR: https://gerrit.nordix.org/c/infra/cicd/+/23508
• Release IPAM (Make release note PR, also check new image is created in quay).
  • Tag PR: 🚀 Release v1.10.0 ip-address-manager#1009
• 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
  • Tag PR: 🚀 Release v0.10.0 baremetal-operator#2417
• Pin Ironic in new release branch in BMO. Make patch release of BMO
  • PR: 🌱 Pin ironic to version 29.0 baremetal-operator#2419
  • PR: 🚀 Release v0.10.1 baremetal-operator#2426
• Bump IPAM and BMO in CAPM3 in main Prior art
  • PR: 🌱 Bump IPAM 1.10.0 and BMO 0.10.0 #2522
• Release CAPM3 (Branch out, add branch protection and required tests, also check new image is created in quay).e2e prior art
  • PR: 🚀 Release v1.10.0 #2530
  • 1.11 e2e support: 🌱 Add support for 1.11 in e2e #2536

Tests and configs

• Add 1.11 to IPAM metadata.yaml in main
  • PR: 🌱 Update 1.11 to metadata.yaml ip-address-manager#1023
• Update dependabot configs:
  • CAPM3 PR: 🌱 add dependabot config for release-1.10 #2527
  • IPAM PR: 🌱 add dependabot config for release-1.10 ip-address-manager#1015
  • BMO PR: 🌱 add dependabot config for release-0.10 baremetal-operator#2427
• 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.10 jobs: https://gerrit.nordix.org/c/infra/cicd/+/23516
  • PR removing 1.7 jobs: https://gerrit.nordix.org/c/infra/cicd/+/23530
• 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 2 3, 4
  • PR IPAM: 🌱 Add IPAM release-1.10 to Prow project-infra#998
  • PR BMO: 🌱 Add BMO release-0.10 to Prow project-infra#1000
  • PR CAPM3: 🌱 Add CAPM3 release-1.10 to Prow project-infra#999
  • PR remove 1.7 tests: 🌱 Remove release-1.7 project-infra#1003
  • PR add triggers to other repos : 🌱 Add other release-1.10 triggers to Prow project-infra#1002
  • Run /test metal3-centos-e2e-integration-test-release-1-10 metal3-ubuntu-e2e-integration-test-release-1-10 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.10 -> main, and update all ironic upgrade tests to use release-0.10, also remove tests for release-0.8 Prior art
  • Add 0.10 PR: 🌱 Add e2e tests for release 0.10 baremetal-operator#2448
• 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.10 and on main. Prior art: 1, 2
  • PR main: 📖 Update docs for release 1.10 #2547
  • PR release-1.10: 📖 Update build badges and triggers in README.md #2548
• Update IPAM README.md with the new e2e triggers, on both the release-1.9 and on main. Prior art: 1, 2 3
  • PR main: 📖 Update release 1.10 to compatibility table ip-address-manager#1025
  • PR release-1.10: 🌱 Update build badges for release-1.10 ip-address-manager#1026
• Update BMO README.md with the new e2e triggers, on both the release-0.10 (if applicable) and on main. Prior art: 1, 2
  • PR main: 📖 Add release-0.10 triggers to README.md baremetal-operator#2446
  • PR release-0.10: 📖 Update badges and e2e triggers in README.md baremetal-operator#2445
• Update Metal3 book. Prior art: 1, 2, 3
  • Release 1.10: PR: 🌱 Update version support tables release-1.10 metal3-docs#516
  • Kubernetes version: Update Kubernetes version to 1.33.0 metal3-docs#523
  • Ironic release: Update versions for ironic-image and IrSO metal3-docs#512
• Announce the releases

Post-release tasks

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

• Add CAPI v1.10 contract. Prior art 1, 2
  • PR: 🌱 Add support for 1.11 in e2e #2536
• Update clusterctl tests to accommodate new releases. prior art 1, 2, 3
  • PR: 🌱 Updating main branch clusterctl tests #2560

[Rozzii]

/triage accepted
/kind 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 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.