Conversation
Signed-off-by: cozystack-bot <[email protected]>
cozystack-bot
requested review from
klinch0,
kvaps and
lllamnyp
as code owners
WalkthroughThis PR updates multiple container image tags and digests across core, system, apps, and extra packages, primarily bumping from v0.36.0-beta.3 to v0.36.0-beta.4 and refreshing several fixed digests. No logic, templates structure, or control-flow changes are introduced. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewersPoem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Please see the documentation for more information. Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).Please share your feedback with us on this Discord post. 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. Comment |
![gemini-code-assist[bot]](proxy.php?url=https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @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, bumping all necessary image tags and version numbers to v0.36.0-beta.4. The changes ensure that all deployed components and their configurations reflect the new beta release, integrating the latest builds and maintaining version consistency across the system.
Highlights
- Image Version Updates: All container image references across various components have been updated to point to the
v0.36.0-beta.4version, along with their corresponding SHA256 digests. This includes images fornginx-cache,kubevirt-csi-driver,installer,e2e-sandbox,matchbox,objectstorage-sidecar,s3manager,cozystack-api,cozystack-controller,dashboard,kubeapps-apis,kamaji,kubeovn-plunger,kubeovn-webhook,kubeovn, andobjectstorage-controller. - Configuration Version Bumps: Key version strings within configuration files have been incremented. Specifically,
cozystackVersioninpackages/system/cozystack-controller/values.yamlandappVersioninpackages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yamlhave been updated fromv0.36.0-beta.3tov0.36.0-beta.4.
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-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-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
-
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. ↩
There was a problem hiding this comment.
Code Review
This pull request prepares for the v0.36.0-beta.4 release by updating various image tags and versions across the repository. The changes are mostly consistent and correct for a release. However, I've identified a critical inconsistency in packages/system/dashboard/values.yaml where an image digest has not been updated along with its tag. This could lead to deploying an older, incorrect version of a component.
| tag: v0.36.0-beta.4 | ||
| digest: "sha256:54906b3d2492c8603a347a5938b6db36e5ed5c4149111cae1804ac9110361947" |
There was a problem hiding this comment.
The image tag has been updated to v0.36.0-beta.4, but the digest on the next line remains unchanged. This will cause an incorrect image version to be deployed, as the digest will take precedence. Please update the digest to match the new image tag.
![coderabbitai[bot]](proxy.php?url=https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
packages/system/seaweedfs/values.yaml (1)
97-112: Ingress host vs TLS hosts mismatch may break SNI/cert selection.Host is "seaweedfs2.demo.cozystack.io" (Line 97) but TLS hosts contain "seaweedfs.demo.cozystack.io" (Line 111). Align them to avoid certificate/name mismatch.
Apply this diff if "seaweedfs2" is intended:
tls: - hosts: - - seaweedfs.demo.cozystack.io + - seaweedfs2.demo.cozystack.io secretName: seaweedfs-s3-ingress-tls
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (18)
packages/apps/http-cache/images/nginx-cache.tag(1 hunks)packages/apps/kubernetes/images/kubevirt-csi-driver.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/seaweedfs/images/objectstorage-sidecar.tag(1 hunks)packages/system/bucket/images/s3manager.tag(1 hunks)packages/system/cozystack-api/values.yaml(1 hunks)packages/system/cozystack-controller/values.yaml(1 hunks)packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml(1 hunks)packages/system/dashboard/values.yaml(2 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/objectstorage-controller/values.yaml(1 hunks)packages/system/seaweedfs/values.yaml(1 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 (19)
packages/apps/http-cache/images/nginx-cache.tag (1)
1-1: Digest bump OK.Pinned to new digest for nginx-cache:0.7.0; no functional changes implied.
packages/core/testing/values.yaml (1)
2-2: e2e image updated to beta.4 — looks good.Pinned tag+digest for test sandbox is consistent with the release version.
packages/system/kubeovn-webhook/values.yaml (1)
3-3: Webhook image bumped to beta.4 — OK.Single FQIN pin avoids drift.
packages/apps/kubernetes/images/kubevirt-csi-driver.tag (1)
1-1: CSI driver digest refresh — OK.No chart logic changes; just a safer pin.
packages/system/kubeovn/values.yaml (1)
67-67: Kube-OVN image digest updated — OK.Tag unchanged (v1.14.5) with new digest; rollout will occur on digest change.
packages/system/dashboard/values.yaml (2)
51-52: kubeapps-apis tag+digest bumped — good.Both tag and digest updated consistently.
22-23: Fix: dashboard tag bumped, but digest not updated — rollout may not change image.Verification script produced no output; confirm the manifest sha256 for ghcr.io/cozystack/cozystack/dashboard:v0.36.0-beta.4 and either update or remove the digest in packages/system/dashboard/values.yaml (lines 22–23).
- Option A — update digest to the correct sha256 for v0.36.0-beta.4 (preferred).
- Option B — remove the digest to rely on the tag (un-pinned).
packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml (1)
79-79: appVersion updated to beta.4 — OK.Matches the release version; keeps the UI/version consistent.
packages/system/objectstorage-controller/values.yaml (1)
3-3: ObjectStorage controller image bumped and pinned — OK.FQIN ensures deterministic deploys.
packages/system/bucket/images/s3manager.tag (1)
1-1: Digest bump looks good; keep it pinned.Tag unchanged (v0.5.0) with new sha256 digest is fine. Please confirm the manifest exists on GHCR and matches expected platforms.
packages/extra/seaweedfs/images/objectstorage-sidecar.tag (1)
1-1: In sync with beta.4; pinned digest—good.Matches the value used in packages/system/seaweedfs/values.yaml Line 121.
packages/system/seaweedfs/values.yaml (1)
121-121: Sidecar image aligned with tag file; OK.Pinned to v0.36.0-beta.4 with digest; consistent across repo.
packages/system/kubeovn-plunger/values.yaml (1)
3-3: Great: moved off ":latest" to a version+digest.Improves reproducibility and supply‑chain hygiene.
packages/system/kubevirt-csi-node/values.yaml (1)
3-4: Digest refresh for 0.29.0—looks fine.Ensure all references to kubevirt-csi-driver across the repo use the same digest (controller/node components, tag files).
packages/core/installer/values.yaml (1)
2-2: Installer bumped to v0.36.0-beta.4 with digest—LGTM.No other config changes detected.
packages/system/kamaji/values.yaml (1)
6-6: Kamaji tag + migrate-image are consistent and pinned.Both point to v0.36.0-beta.4 with the same digest—good for rollback determinism.
Also applies to: 16-16
packages/system/cozystack-controller/values.yaml (1)
2-2: Controller image bump looks correct and pinned — verification script failed; fix and re-runValues.yaml shows the controller image pinned to v0.36.0-beta.4@sha256:..., but the supplied GHCR manifest-check script failed to validate manifests: get_repo left the tag/digest in the repository name (token request returned 403, manifest fetch returned 404). Fix repo extraction to strip an optional "ghcr.io/" and any trailing ":tag" or "@digest" (e.g. repo=$(echo "$img" | sed -E 's#^ghcr.io/##; s#(:|@).*##')), then re-run the manifest, stale-version, and pinning checks.
packages/extra/bootbox/images/matchbox.tag (1)
1-1: Verify GHCR digest and multi-arch manifestImage bump LGTM; the verification script couldn't run because skopeo/crane isn't installed — run the provided skopeo/crane check locally and confirm the manifest lists linux/amd64 and linux/arm64.
packages/system/cozystack-api/values.yaml (1)
2-2: Approve: API image bump — no v0.36.0-beta.3 references found.
packages/system/cozystack-api/values.yaml updated to v0.36.0-beta.4; repo-wide search returned no matches.
2 participants
This PR prepares the release
v0.36.0-beta.4.Summary by CodeRabbit