Stackable Release 24.7

Known issues

• Secret secret-provisioner-tls-ca needs to move to the stackable-operators namespace (see issue in stretch goals).

Release checklists

General pre-requisites (before feature freeze)

• 2024-07-08 to 2024-07-12
• Update products for 24.7 #594
• Run integration tests for all products once with ARM #519
• chore: bump rust-toolchain to 1.79.0 operator-templating#406
• chore: Bump rust-toolchain to 1.79.0, and bump crate dependencies operator-rs#822
• chore: Pre 24.7 releases operator-rs#823
• Bump cargo dependencies in all operators #601
• 2024-07-15 to 2024-07-19
• Run/check getting-started scripts #603
• fix: Update demos and documentation demos#57
• Ensure integration tests are successful on OpenShift #608
• Check demos and upgrade from 24.3 to dev release demos#59
• chore: Bump Rust and Go dependencies stackablectl#307
• docs: Promote user-info-fetcher docs to navgation opa-operator#557
• Prevent double logging of the airflow container logs airflow-operator#474
• Adjust signature verification policy documentation#629

Other release-specific pre-requisites

• fix: Re-create shared internal secret with a new name druid-operator#590
• Stretch goal Reuse an existing TLS CA from a previous installation secret-operator#453

Feature freeze

This will not be so crucial with release branches, but is nonetheless sensible as it will make it easier to cherry-pick any release-related bugfixes from main into the release branch.

End of the release cycle (Release day)

Technical tasks

• Create release branches for docker-images (see stackable-utils for script to create branches)
• Create release tag(s) for docker-images (see stackable-utils for scripts to create tags)
• Create release branches for operators (see stackable-utils for script to create branches)
• Create release tag(s) for operators (see stackable-utils for scripts to create tags)
• chore: Release stackablectl-24.7.0 stackablectl#309
• Update changelogs in main branches (see stackable-utils for script to do this)
• chore: Add release 24.7.0 crddocs#38
• Add 24.7 release to release.yaml release#30
• Run/check getting-started scripts + integration tests for 24.7 #613
• Check demos and upgrade from 24.3 to 24.7 release demos#65
• Test with locally updated (to new release number) releases.yaml
• Check that an upgrade can be performed on an existing cluster without data loss.

Documentation tasks

• docs: release notes for 24.7 documentation#631
• Check the Changelog and/or issue labels to compile Release Highlights
• Upgrade guide: Document how to use stackablectl to uninstall all and install new release
• Upgrade guide: Document how to use helm to uninstall all and install new release
• Upgrade guide: Every breaking change of all our operators
• Upgrade guide: List dropped supported product versions (if there are some)
• Upgrade guide: List dropped supported operators (if there are some)
• Upgrade guide: List supported k8s versions
• docs(getting-started): Update version references documentation#633
• Run release scripts for documentation Add release branches to the playbooks for release 24.7 documentation#635
• Set the release to "Released" in the Feature Tracker and create a new release
• Document breaking changes of JVM metrics https://github.com/prometheus/jmx_exporter/releases/tag/1.0.1
• Document Superset 2.1.3 is not supported on ARM because of Postgres version problems (ask Maxi)
• fix: remove home: from refs documentation#637

Marketing tasks can now reference published documentation.

Marketing tasks

• Write marketing / customer oriented release summary to be published in the marketing channels
• Update the homepage banner (as long as we have it) to point to the new release
• Write a blogpost / news article announcing the new release (optional)
• Write a description of new demos for homepage/demos section
• Announce Release in Newsletter (optional)
• Produce a release highlight video (optional)
• Announce Release on Hacker News (optional)
• Post an announcement in the GitHub Discussions Announcement forum and make it a pinned discussion while at the same time removing the old pinned thread
• Post an announcement in Discord
• Post an announcement on DOK Community in the #be-shameless Channel (Ping Lars or Jim)
• Post an announcement via OSBA (Ping Lars)
• Send announcement to Kubernetes Podcast (Ping Lars)
• Send announcement to Heise
• Ping the stackable-ionos-tech channel or anyone responsible once all tags are created

Post-release tasks

• Update the list of supported SDP versions in Jira @Jimvin
• Bump Rust version. This can be done in this file by changing rust_version and also for the ubi base image here. Please be aware that this action will change it for all repositories at the same time (when merging the templating PRs).
• Check/bump versions of kube-rs and k8s-openapi (also checking the version of k8s we build against)
• Check/bump ubi8 base image
• Bump preflight version to 1.10.0 #631
• Openshift certification 24.7.0 #625
• Define product versions to include in the next release
• Add branch protection to release branches once they are stable Modify the release process to avoid branch protection errors stackable-utils#81
• Release Retro | Issues, Problems and needed fixes we stumbled across as a discussion #615