Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS WC Release 19.3.2 #3243

Closed
22 tasks
T-Kukawka opened this issue Feb 15, 2024 · 0 comments
Closed
22 tasks

AWS WC Release 19.3.2 #3243

T-Kukawka opened this issue Feb 15, 2024 · 0 comments
Assignees
Labels

Comments

@T-Kukawka
Copy link
Contributor

T-Kukawka commented Feb 15, 2024

ℹ️ Team Phoenix is drafting AWS v19.3.2 with Kubernetes v1.24 support.
Target release date: 2024-02-29.
Release PR: ...

Scope

Testing

  • Check that Cilium works fine with this OS release

Pre-Release

  • Create release ticket on Releases board
  • Make an announcement on #sig-product that team is doing a release. Include a link to the ticket from the release board.
  • Make sure release was tested by creating new cluster, upgrading from older version and with HelloWorld app.
  • Aggregate release notes from all changed components and add to README.md in the release directory.
  • Send draft release announcement to #sig-product for review ASAP.
  • Verify documentation is up to date.

Releasing

  • Create release PR
    Instructions
    • Define new release in release.yaml file.
    • Activate new release by setting state to active.
    • Deactivate old release if it's within same major version (state: deprecated). Verify with PO if you have doubts.
    • Check versions of all components included. They shouldn't be lower than those in the previous release unless there was a rollback.

Example PR

  • Release relevant operators.
    • Tag release branch.
    • Bump operator version in draft release.
  • Make sure that WIP releases in releases repo branch are removed and not merged to master since the master branch is deployed automatically after merging PR and that would make WIP releases visible in customers’ installations which should generally not happen.

Post-Release

  • Update front-end cluster with the new release.
  • Verify release is available on all installations. You can use this script.
  • Send out release announcement to all customers according to these instructions.
  • PO subscribes to release posts on Slack to get notifications if there are follow-up messages.
  • Close release task on Releases board.
@github-project-automation github-project-automation bot moved this to Inbox 📥 in Roadmap Feb 15, 2024
@whites11 whites11 self-assigned this Feb 26, 2024
@T-Kukawka T-Kukawka assigned T-Kukawka and unassigned whites11 Feb 28, 2024
@github-project-automation github-project-automation bot moved this from Inbox 📥 to Done ✅ in Roadmap Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

2 participants