Skip to content

Release v0.37.0-beta.1 - #1490

Merged
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
release-0.37.0-beta.1
Oct 6, 2025
Merged

Release v0.37.0-beta.1#1490
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
release-0.37.0-beta.1

Conversation

@cozystack-bot

@cozystack-bot Cozystack Bot (cozystack-bot) commented Oct 6, 2025

Copy link
Copy Markdown
Contributor

This PR prepares the release v0.37.0-beta.1.

Summary by CodeRabbit

  • Chores
    • Pinned multiple container images from “latest” to specific versions and refreshed digests for improved stability and reproducibility.
    • Upgraded core components from v0.37.0-alpha.2 to v0.37.0-beta.1 across installer, API, controller, dashboard services, Kamaji, kubeovn tools, and object storage sidecar/controller.
    • Updated Cilium to 1.17.8 and refreshed digests for KubeOVN, MetalLB, Grafana, and related apps.
  • Documentation
    • Dashboard branding text updated to display v0.37.0-beta.1.

Signed-off-by: cozystack-bot <217169706+cozystack-bot@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Oct 6, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

This PR updates numerous container image references across the repository, pinning tags (e.g., latest → specific versions), updating digests, and bumping components from v0.37.0-alpha.2 to v0.37.0-beta.1. One indentation fix appears under seaweedfs s3.extraArgs. No control-flow or logic changes are introduced.

Changes

Cohort / File(s) Summary of changes
App images: pin/tag updates
packages/apps/clickhouse/images/clickhouse-backup.tag, packages/apps/http-cache/images/nginx-cache.tag, packages/apps/kubernetes/images/cluster-autoscaler.tag, .../kubevirt-cloud-provider.tag, .../kubevirt-csi-driver.tag, .../ubuntu-container-disk.tag, packages/apps/mysql/images/mariadb-backup.tag
Pins image tags (latest → 0.0.0 or v1.33) and/or updates digests.
Core: installer & testing
packages/core/installer/values.yaml, packages/core/testing/values.yaml
Bumps images from v0.37.0-alpha.2 → v0.37.0-beta.1 with new digests.
System: platform components
packages/system/cozystack-api/values.yaml, packages/system/cozystack-controller/values.yaml, packages/system/dashboard/values.yaml, packages/system/dashboard/templates/configmap.yaml, packages/system/kamaji/values.yaml, packages/system/objectstorage-controller/values.yaml, packages/system/seaweedfs/values.yaml, packages/system/bucket/images/s3manager.tag, packages/system/kubevirt-csi-node/values.yaml
Version bumps alpha.2 → beta.1; updates digests; dashboard text updated; seaweedfs extraArgs indentation adjusted; s3manager digest updated; kubevirt-csi-node pins image.
System: networking stack
packages/system/cilium/values.yaml, packages/system/kubeovn/values.yaml, packages/system/kubeovn-plunger/values.yaml, packages/system/kubeovn-webhook/values.yaml, packages/system/metallb/values.yaml
Cilium tag pinned (latest → 1.17.8) with digest; KubeOVN plunger/webhook to beta.1; KubeOVN and Metallb digests updated.
Extras: images
packages/extra/bootbox/images/matchbox.tag, packages/extra/monitoring/images/grafana.tag, packages/extra/seaweedfs/images/objectstorage-sidecar.tag
Updates image tags/digests; bumps alpha.2 → beta.1 where applicable; pins grafana to specific tag.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • kvaps
  • lllamnyp
  • klinch0

Poem

A rabbit thumps: “Tags aligned!”
From alpha to beta, neatly signed.
Digests fresh, no code to fear,
Images pinned, the path is clear.
I nibble greens, then hop away —
Release trains roll without delay. 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title “Release v0.37.0-beta.1” clearly and concisely communicates the primary purpose of the changeset, which is to prepare and tag the beta release version, and aligns directly with the pull request objectives without including extraneous details.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch release-0.37.0-beta.1

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1ee3d00 and 458ca63.

📒 Files selected for processing (26)
  • packages/apps/clickhouse/images/clickhouse-backup.tag (1 hunks)
  • packages/apps/http-cache/images/nginx-cache.tag (1 hunks)
  • packages/apps/kubernetes/images/cluster-autoscaler.tag (1 hunks)
  • packages/apps/kubernetes/images/kubevirt-cloud-provider.tag (1 hunks)
  • packages/apps/kubernetes/images/kubevirt-csi-driver.tag (1 hunks)
  • packages/apps/kubernetes/images/ubuntu-container-disk.tag (1 hunks)
  • packages/apps/mysql/images/mariadb-backup.tag (1 hunks)
  • packages/core/installer/values.yaml (1 hunks)
  • packages/core/testing/values.yaml (1 hunks)
  • packages/extra/bootbox/images/matchbox.tag (1 hunks)
  • packages/extra/monitoring/images/grafana.tag (1 hunks)
  • packages/extra/seaweedfs/images/objectstorage-sidecar.tag (1 hunks)
  • packages/system/bucket/images/s3manager.tag (1 hunks)
  • packages/system/cilium/values.yaml (1 hunks)
  • packages/system/cozystack-api/values.yaml (1 hunks)
  • packages/system/cozystack-controller/values.yaml (1 hunks)
  • packages/system/dashboard/templates/configmap.yaml (1 hunks)
  • packages/system/dashboard/values.yaml (1 hunks)
  • packages/system/kamaji/values.yaml (2 hunks)
  • packages/system/kubeovn-plunger/values.yaml (1 hunks)
  • packages/system/kubeovn-webhook/values.yaml (1 hunks)
  • packages/system/kubeovn/values.yaml (1 hunks)
  • packages/system/kubevirt-csi-node/values.yaml (1 hunks)
  • packages/system/metallb/values.yaml (1 hunks)
  • packages/system/objectstorage-controller/values.yaml (1 hunks)
  • packages/system/seaweedfs/values.yaml (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Prepare environment
🔇 Additional comments (22)
packages/core/installer/values.yaml (1)

2-2: LGTM! Standard beta release version bump.

The installer image has been correctly updated from alpha to beta with the corresponding digest update.

packages/system/kubeovn-plunger/values.yaml (1)

3-3: LGTM! Standard beta release version bump.

The kubeovn-plunger image has been correctly updated to the beta version with the corresponding digest.

packages/extra/seaweedfs/images/objectstorage-sidecar.tag (1)

1-1: LGTM! Standard beta release version bump.

The objectstorage-sidecar image reference has been correctly updated to the beta version.

packages/system/kubeovn-webhook/values.yaml (1)

3-3: LGTM! Standard beta release version bump.

The kubeovn-webhook image has been correctly updated to the beta version with the corresponding digest.

packages/apps/kubernetes/images/cluster-autoscaler.tag (1)

1-1: Verify the "0.0.0" version tag is intentional.

Pinning from latest to a specific version is good practice for reproducibility. However, "0.0.0" is an unusual semantic version that typically indicates a placeholder or development build.

Please confirm this version tag is intentional and aligns with your versioning strategy for cluster-autoscaler.

packages/system/cozystack-api/values.yaml (1)

2-2: LGTM! Standard beta release version bump.

The cozystack-api image has been correctly updated to the beta version with the corresponding digest.

packages/apps/kubernetes/images/kubevirt-cloud-provider.tag (1)

1-1: Verify the "0.0.0" version tag is intentional.

Similar to cluster-autoscaler, this change pins the image from latest to "0.0.0", which is an unconventional semantic version.

Please confirm this version tag follows your intended versioning strategy for kubevirt-cloud-provider.

packages/core/testing/values.yaml (1)

2-2: LGTM! Standard beta release version bump.

The e2e-sandbox image has been correctly updated to the beta version with the corresponding digest.

packages/system/kubeovn/values.yaml (1)

67-67: LGTM!

The digest update for the kubeovn v1.14.5 image maintains version pinning with digest-based reproducibility, which is a good practice for release stability.

packages/apps/mysql/images/mariadb-backup.tag (1)

1-1: Verify the "0.0.0" version tag.

Moving from "latest" to a pinned version improves reproducibility. However, the "0.0.0" version tag is unconventional. Ensure this is intentional and not a placeholder that should use proper semantic versioning (e.g., "1.0.0").

packages/system/objectstorage-controller/values.yaml (1)

3-3: LGTM!

The version bump from alpha.2 to beta.1 aligns with the release objectives and maintains digest-based image pinning for reproducibility.

packages/system/cozystack-controller/values.yaml (2)

2-2: LGTM!

The image reference update from v0.37.0-alpha.2 to v0.37.0-beta.1 is consistent with the release objectives.


5-5: LGTM!

The cozystackVersion string properly matches the image tag version, maintaining consistency across configuration.

packages/system/dashboard/templates/configmap.yaml (1)

3-3: LGTM!

The tenant text version update from v0.37.0-alpha.2 to v0.37.0-beta.1 aligns with the overall release version bump.

packages/system/bucket/images/s3manager.tag (1)

1-1: LGTM!

The digest update for s3manager v0.5.0 maintains version pinning with updated content hash, ensuring reproducible deployments.

packages/system/dashboard/values.yaml (1)

2-6: LGTM!

All three dashboard service images (openapiUI, openapiUIK8sBff, tokenProxy) are consistently updated from v0.37.0-alpha.2 to v0.37.0-beta.1 with refreshed digests, maintaining alignment with the release objectives.

packages/apps/clickhouse/images/clickhouse-backup.tag (1)

1-1: Verify the "0.0.0" version tag.

Pinning the version instead of using "latest" improves reproducibility. However, similar to mariadb-backup.tag, the "0.0.0" version is unconventional. Confirm this version choice is intentional and aligns with your versioning strategy.

packages/extra/bootbox/images/matchbox.tag (1)

1-1: Version bump to beta.1 is correct.

The matchbox image has been updated from alpha.2 to beta.1 with a new digest, consistent with this release PR's objectives.

packages/apps/kubernetes/images/ubuntu-container-disk.tag (1)

1-1: Excellent: pinning from latest to a specific version.

Replacing the latest tag with v1.33 improves build reproducibility and prevents unexpected changes from upstream updates.

packages/system/kamaji/values.yaml (1)

6-6: Beta version updates are consistent.

Both the main image tag and the --migrate-image argument have been updated to v0.37.0-beta.1 with matching digests, ensuring consistency across the Kamaji deployment.

Also applies to: 16-16

packages/system/metallb/values.yaml (1)

7-7: MetalLB image digests updated – please verify existence
Controller and speaker remain at v0.15.2 with new sha256 digests; confirm both digests exist in ghcr.io.

packages/apps/http-cache/images/nginx-cache.tag (1)

1-1: Approve update; verify GHCR manifest availability
Unauthenticated HEAD returns 401—authenticate to ghcr.io (e.g., docker login or crane with auth) and confirm the sha256:c1944c60… manifest exists.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello Cozystack Bot (@cozystack-bot), I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is a standard release preparation, specifically for v0.37.0-beta.1. It systematically updates version strings and container image references across various core and optional components of the system. The primary goal is to ensure all parts of the platform are pointing to the correct and latest builds for the upcoming beta release, facilitating consistent deployments and testing.

Highlights

  • Version Update: The pull request updates numerous internal component image tags and version references from v0.37.0-alpha.2 to v0.37.0-beta.1 to align with the new release.
  • Image Digest Refresh: Many container image SHA256 digests have been updated across various applications and system components, ensuring that the release points to the latest builds.
  • Cilium Version Bump: The Cilium network plugin image tag has been specifically updated from latest to 1.17.8, along with its new SHA256 digest.
  • Ubuntu Container Disk Version: The ubuntu-container-disk image tag has been updated from latest to v1.33 with a new SHA256 digest.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment Gemini (@gemini-code-assist) Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request prepares for the v0.37.0-beta.1 release by updating various version strings and image tags. The changes are mostly consistent with a release process. My main feedback is around the image tagging strategy. Several images are being retagged from latest to 0.0.0. While removing the latest tag is a good practice, using a generic 0.0.0 tag is not ideal for maintainability and traceability. I've left specific suggestions to use more descriptive tags based on the software version being built or the base image version, where this information is readily available in the corresponding Dockerfiles.

@@ -1 +1 @@
ghcr.io/cozystack/cozystack/clickhouse-backup:latest@sha256:0f8707d348e03bfa7589159a61d781d4eca238bdfff5dc09f4d3a01b31285a55
ghcr.io/cozystack/cozystack/clickhouse-backup:0.0.0@sha256:3faf7a4cebf390b9053763107482de175aa0fdb88c1e77424fd81100b1c3a205

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To improve clarity, it's better to use a specific version tag instead of 0.0.0. This image is based on clickhouse/clickhouse-server:24.8.4-alpine, so using a tag like 24.8.4 would be more descriptive.

ghcr.io/cozystack/cozystack/clickhouse-backup:24.8.4@sha256:3faf7a4cebf390b9053763107482de175aa0fdb88c1e77424fd81100b1c3a205

@@ -1 +1 @@
ghcr.io/cozystack/cozystack/cluster-autoscaler:latest@sha256:89f822343654ea66efb3ac50bf72b483a52c1a11d33497fdfac5bbd0f3715c2b
ghcr.io/cozystack/cozystack/cluster-autoscaler:0.0.0@sha256:2d39989846c3579dd020b9f6c77e6e314cc81aa344eaac0f6d633e723c17196d

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While pinning to a digest is a great practice for reproducibility, using a generic tag like 0.0.0 can be confusing. The Dockerfile for this image builds cluster-autoscaler-1.32.0. It would be more descriptive and maintainable to use a tag that reflects the version of the software being packaged, such as 1.32.0.

ghcr.io/cozystack/cozystack/cluster-autoscaler:1.32.0@sha256:2d39989846c3579dd020b9f6c77e6e314cc81aa344eaac0f6d633e723c17196d

@@ -1 +1 @@
ghcr.io/cozystack/cozystack/kubevirt-cloud-provider:latest@sha256:190b7d231da1dfbded3af77777cc99b93a29a36ea69186170460f09d533fe041
ghcr.io/cozystack/cozystack/kubevirt-cloud-provider:0.0.0@sha256:5335c044313b69ee13b30ca4941687e509005e55f4ae25723861edbf2fbd6dd2

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While pinning to a digest is a great practice, using a generic tag like 0.0.0 can be confusing. The latest tag is being correctly removed, but it would be more descriptive to use a tag that reflects the version of the software being packaged. Since this image is built from a specific git commit (a0acf33), consider using the short commit hash as the tag (e.g., a0acf33) for better traceability.

ghcr.io/cozystack/cozystack/kubevirt-cloud-provider:a0acf33@sha256:5335c044313b69ee13b30ca4941687e509005e55f4ae25723861edbf2fbd6dd2

@@ -1 +1 @@
ghcr.io/cozystack/cozystack/kubevirt-csi-driver:latest@sha256:7312623d19d9a7dc80da73f53a1aabb769796674e5899aad5c0d6100f351d0e8
ghcr.io/cozystack/cozystack/kubevirt-csi-driver:0.0.0@sha256:6d3fc4246928f65e784cd8822457c505a8a3742b51a072ebdb43d9570ec10b39

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While pinning to a digest is a great practice, using a generic tag like 0.0.0 can be confusing. The latest tag is being correctly removed, but it would be more descriptive to use a tag that reflects the version of the software being packaged. Since this image is built from a specific git commit (a8d6605b...), consider using the short commit hash as the tag (e.g., a8d6605b) for better traceability.

ghcr.io/cozystack/cozystack/kubevirt-csi-driver:a8d6605b@sha256:6d3fc4246928f65e784cd8822457c505a8a3742b51a072ebdb43d9570ec10b39

@@ -1 +1 @@
ghcr.io/cozystack/cozystack/grafana:latest@sha256:dc27b9d7ef42e3d59667a203cb94d410c60afc119102ff1b9a081af4ea72f52c
ghcr.io/cozystack/cozystack/grafana:0.0.0@sha256:c63978e1ed0304e8518b31ddee56c4e8115541b997d8efbe1c0a74da57140399

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Using a specific version tag instead of 0.0.0 improves clarity and maintainability. Since this image is based on grafana/grafana:11.4.0, it would be better to use 11.4.0 as the tag.

ghcr.io/cozystack/cozystack/grafana:11.4.0@sha256:c63978e1ed0304e8518b31ddee56c4e8115541b997d8efbe1c0a74da57140399

storageClass: replicated
csiDriver:
image: ghcr.io/cozystack/cozystack/kubevirt-csi-driver:latest@sha256:7312623d19d9a7dc80da73f53a1aabb769796674e5899aad5c0d6100f351d0e8
image: ghcr.io/cozystack/cozystack/kubevirt-csi-driver:0.0.0@sha256:6d3fc4246928f65e784cd8822457c505a8a3742b51a072ebdb43d9570ec10b39

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Using the latest tag is a bad practice, and it's good that it's being replaced. However, 0.0.0 is not a descriptive tag. Consider using a tag that reflects the source, for example, by using a short git SHA from the build (a8d6605b), to improve traceability and maintainability.

  image: ghcr.io/cozystack/cozystack/kubevirt-csi-driver:a8d6605b@sha256:6d3fc4246928f65e784cd8822457c505a8a3742b51a072ebdb43d9570ec10b39

@kvaps
Andrei Kvapil (kvaps) merged commit dfcdf19 into main Oct 6, 2025
20 checks passed
@kvaps
Andrei Kvapil (kvaps) deleted the release-0.37.0-beta.1 branch October 6, 2025 21:02
@coderabbitai coderabbitai Bot mentioned this pull request Oct 9, 2025
@coderabbitai coderabbitai Bot mentioned this pull request Jan 20, 2026
@coderabbitai coderabbitai Bot mentioned this pull request Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release Releasing a new Cozystack version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants