Need to create a release-1.31 track

[addyess]

Summary

Make sure to follow the steps below and ensure all actions are completed and signed-off by one team member.

Information

• K8s version: 1.xx

• Owner: @addyess

• Reviewer: @bschimke95 or @canonical/kubernetes

• PR: https://github.com/canonical/k8s-snap/pull/667
• PR: https://github.com/canonical/k8s-snap/pull/668

Actions

The steps are to be followed in-order, each task must be completed by the person specified in bold. Do not perform any steps unless all previous ones have been signed-off. The Reviewer closes the issue once all steps are complete.

• [x] Owner: Add the assignee and reviewer as assignees to the GitHub issue

• [x] Owner: Ensure that you are part of the "containers" team

• [x] Owner: Request a new 1.xx Snapstore track for the snaps similar to the snapstore track-request.

  • Post template on https://discourse.charmhub.io/

  Title: Request for 1.xx tracks for the k8s snap

  Category: store-requests

  Body:

  Hi,

  Could we please have a track "1.xx-classic" and "1.xx" for the respective K8s snap release?

  Thank you, $name

• [x] Owner: Create release-1.xx branch from latest main

  • git switch main
  • git pull
  • git checkout -b release-1.xx
  • git push origin release-1.xx

• [x] Owner: Create release-1.xx branch from latest master in k8s-dqlite

  • git clone git@github.com:canonical/k8s-dqlite.git ~/tmp/release-1.xx
  • pushd ~/tmp/release-1.xx
  • git switch master
  • git pull
  • git checkout -b release-1.xx
  • git push origin release-1.xx
  • popd
  • rm -rf ~/tmp/release-1.xx

• [x] Owner: Create release-1.xx branch from latest main in cilium-rocks

  • git clone git@github.com:canonical/cilium-rocks.git ~/tmp/release-1.xx
  • pushd ~/tmp/release-1.xx
  • git switch main
  • git pull
  • git checkout -b release-1.xx
  • git push origin release-1.xx
  • popd
  • rm -rf ~/tmp/release-1.xx

• [x] Owner: Create release-1.xx branch from latest main in coredns-rock

  • git clone git@github.com:canonical/coredns-rock.git ~/tmp/release-1.xx
  • pushd ~/tmp/release-1.xx
  • git switch main
  • git pull
  • git checkout -b release-1.xx
  • git push origin release-1.xx
  • popd
  • rm -rf ~/tmp/release-1.xx

• [x] Owner: Create release-1.xx branch from latest main in metrics-server-rock

  • git clone git@github.com:canonical/metrics-server-rock.git ~/tmp/release-1.xx
  • pushd ~/tmp/release-1.xx
  • git switch main
  • git pull
  • git checkout -b release-1.xx
  • git push origin release-1.xx
  • popd
  • rm -rf ~/tmp/release-1.xx

• [x] Owner: Create release-1.xx branch from latest main in rawfile-localpv

  • git clone git@github.com:canonical/rawfile-localpv.git ~/tmp/release-1.xx
  • pushd ~/tmp/release-1.xx
  • git switch rockcraft
  • git pull
  • git checkout -b release-1.xx
  • git push origin release-1.xx
  • popd
  • rm -rf ~/tmp/release-1.xx

• [x] Reviewer: Ensure release-1.xx branch is based on latest changes on main at the time of the release cut.

• [x] Owner: Create PR to initialize release-1.xx branch:

  • [x] Update KUBERNETES_RELEASE_MARKER to stable-1.xx in /build-scripts/hack/update-component-versions.py
  • [x] Update master to release-1.xx in /build-scripts/components/k8s-dqlite/version
  • not needed since https://github.com/canonical/k8s-snap/pull/644
  • [x] Update "main" to "release-1.xx" in /build-scripts/hack/generate-sbom.py
  • [x] git commit -m 'Release 1.xx'
  • [x] Create PR against release-1.xx with the changes and request review from Reviewer. Make sure to update the issue Information section with a link to the PR.

• [x] Reviewer: Review and merge PR to initialize branch.

• [x] Owner: Create PR to initialize update-components.yaml job for release-1.xx branch:

  • [x] Add release-1.xx in .github/workflows/update-components.yaml
  • [x] Remove unsupported releases from the list (if applicable, consult with Reviewer)
  • [x] Create PR against main with the changes and request review from Reviewer. Make sure to update the issue information with a link to the PR.

• [x] Reviewer: On merge, confirm Auto-update strict branch action runs to completion and that the autoupdate/release-1.xx-* flavor branches are created.

  • [x] autoupdate/release-1.xx-strict
  • [x] autoupdate/release-1.xx-moonray

• [x] Owner: Create launchpad builders for release-1.xx and flavors

  • [x] Run the Confirm Snap Builds Action

• [x] Reviewer: Ensure snap recipes are created in lp:k8s/+snaps

  • [x] look for k8s-snap-1.xx-classic
  • [x] look for k8s-snap-1.xx-strict
  • [x] look for k8s-snap-1.xx-moonray
  • [x] make sure each is "Authorized for Store Upload"

After release

• [x] Owner follows up with the Reviewer and team about things to improve around the process.
• [ ] Owner: After a few weeks of stable CI, update default track to 1.xx/stable via
  • On the snap [releases page][], select Track > 1.xx
• [x] Reviewer: Ensure snap recipes are created in lp:k8s/+snaps

[addyess]

I want to update this issue template once we complete it.

[bschimke95]

For the new template: The "Reviewer: Ensure snap recipes are created in 'lp:k8s/+snaps'" check is listed twice (in Actions and in Post Release)

[bschimke95]

LGTM, issue can be closed (check After a few weeks of stable CI, update default track to 1.xx/stable via... is currently not applicable because we don't have a stable release yet)

[addyess]

Thanks Ben.... I appreciate it. Let's close when #677 is merged

[addyess]

I want to update this issue template once we complete it.