Conversation
Signed-off-by: cozystack-bot <[email protected]>
cozystack-bot
requested review from
klinch0,
kvaps and
lllamnyp
as code owners
|
Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. WalkthroughThis PR updates container image tags and digests across multiple components. Several images move from v0.35.0-alpha.3 to v0.35.0-beta.1, Kubernetes components bump from 0.26.2 to 0.26.3, and some digests are refreshed without tag changes. No logic or configuration structure changes. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![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 dedicated to preparing the v0.35.0-beta.1 release. It primarily involves updating numerous image tags and their corresponding SHA256 digests across various components and applications within the Cozystack ecosystem. The changes ensure that all referenced container images and internal version indicators are aligned with the new beta release, moving from the previous alpha state.
Highlights
- Core Component Version Updates: All core Cozystack components, including the installer, API, controller, dashboard, and testing sandbox, have been updated to the new
v0.35.0-beta.1release tag. - Application Image Updates: Several application-specific images, such as
clickhouse-backup,cluster-autoscaler,kubevirt-cloud-provider, andkubevirt-csi-driver, have been updated to their latest minor or patch versions. - Image Digest Updates: Various image SHA256 digests were updated across the repository, including for
nginx-cache,s3manager, andkubeovn, ensuring that specific, verified image builds are referenced. - Configuration Version Alignment: The
appVersionwithin the dashboard's configuration has been aligned with the newv0.35.0-beta.1release.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| 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 issue 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 the release v0.35.0-beta.1 by updating various image tags and versions across the repository. While most changes appear correct, I've identified two critical issues where image tags were updated to new versions, but their corresponding SHA256 digests were not. This could lead to deploying incorrect or outdated software versions. Please review and correct these inconsistencies.
| @@ -1 +1 @@ | |||
| ghcr.io/cozystack/cozystack/clickhouse-backup:0.11.1@sha256:3faf7a4cebf390b9053763107482de175aa0fdb88c1e77424fd81100b1c3a205 | |||
| ghcr.io/cozystack/cozystack/clickhouse-backup:0.12.0@sha256:3faf7a4cebf390b9053763107482de175aa0fdb88c1e77424fd81100b1c3a205 | |||
There was a problem hiding this comment.
The image tag has been updated from 0.11.1 to 0.12.0, but the SHA256 digest has not changed. A new image version should have a new digest. This is likely incorrect and could lead to deploying an older version of the software.
| @@ -1 +1 @@ | |||
| ghcr.io/cozystack/cozystack/kubevirt-cloud-provider:0.26.2@sha256:5335c044313b69ee13b30ca4941687e509005e55f4ae25723861edbf2fbd6dd2 | |||
| ghcr.io/cozystack/cozystack/kubevirt-cloud-provider:0.26.3@sha256:5335c044313b69ee13b30ca4941687e509005e55f4ae25723861edbf2fbd6dd2 | |||
There was a problem hiding this comment.
The image tag has been updated from 0.26.2 to 0.26.3, but the SHA256 digest has remained the same. This is likely an error, as a new version of an image should have a different digest. The digest should be updated to match the new image version.
![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: 1
♻️ Duplicate comments (2)
packages/apps/kubernetes/images/kubevirt-cloud-provider.tag (1)
1-1: Potential mismatch: tag bumped to 0.26.3 but digest unchanged from 0.26.2.New image versions typically have different digests. Please verify and update the digest to match 0.26.3.
Run this script to compare GHCR manifest digests for 0.26.2 vs 0.26.3:
#!/bin/bash set -euo pipefail repo="cozystack/cozystack/kubevirt-cloud-provider" accept='Accept: application/vnd.oci.image.manifest.v1+json, application/vnd.docker.distribution.manifest.v2+json' for tag in 0.26.2 0.26.3; do digest=$(curl -sI -H "$accept" "https://ghcr.io/v2/${repo}/manifests/${tag}" \ | awk -F': ' 'tolower($1)=="docker-content-digest"{print $2}' | tr -d '\r') echo "${tag} digest: ${digest}" done echo "Pinned in repo: sha256:5335c044313b69ee13b30ca4941687e509005e55f4ae25723861edbf2fbd6dd2"packages/apps/clickhouse/images/clickhouse-backup.tag (1)
1-1: Critical: Version bump without digest changeThe image tag updated from 0.11.1 to 0.12.0 but the SHA256 digest remains unchanged. A new image version should have a new digest, as this indicates different content. This could result in deploying an incorrect version.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (20)
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/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(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)
🔇 Additional comments (17)
packages/core/testing/values.yaml (1)
2-2: LGTM: e2e image bumped to v0.35.0-beta.1 with digest pin.No functional changes; pinned digest is good for reproducibility.
packages/system/kubeovn/values.yaml (1)
67-67: LGTM: kube-ovn digest updated while tag remains v1.13.14.Digest pinning is correct; no other config changes observed.
packages/system/kubeovn-webhook/values.yaml (1)
3-3: LGTM: kubeovn-webhook updated to v0.35.0-beta.1 with new digest.Straightforward image bump with digest pinning.
packages/apps/http-cache/images/nginx-cache.tag (1)
1-1: LGTM: nginx-cache digest updated (tag unchanged).Digest pinning maintained; change is consistent with a rebuild or base update.
packages/apps/kubernetes/images/cluster-autoscaler.tag (1)
1-1: LGTM: cluster-autoscaler updated to 0.26.3 with new digest.Version bump and digest pin look correct.
packages/core/installer/values.yaml (1)
2-2: LGTM: installer moved to v0.35.0-beta.1 with digest pin.Matches the release preparation objective.
packages/system/seaweedfs/values.yaml (1)
119-119: LGTM: seaweedfs COSI sidecar updated to v0.35.0-beta.1 with digest.Change is aligned with other beta bumps in the PR.
packages/system/bucket/images/s3manager.tag (1)
1-1: LGTM - Proper digest update for image rebuildThe digest update while maintaining the same tag version (v0.5.0) indicates a proper image rebuild, which is standard practice for maintenance updates or dependency refreshes.
packages/extra/seaweedfs/images/objectstorage-sidecar.tag (1)
1-1: LGTM - Consistent alpha to beta version updateThe update from v0.35.0-alpha.3 to v0.35.0-beta.1 with corresponding digest change aligns perfectly with the PR's release preparation objective.
packages/apps/kubernetes/images/kubevirt-csi-driver.tag (1)
1-1: LGTM - Proper version bump with digest updateThe update from 0.26.2 to 0.26.3 with corresponding digest change represents a proper minor version upgrade. This change is consistent with related updates in the kubevirt-csi-node values.
packages/system/kubevirt-csi-node/values.yaml (1)
3-3: LGTM - Consistent CSI driver version updateThe kubevirt-csi-driver image update to 0.26.3 is consistent with the corresponding tag file and includes the proper digest update.
packages/system/kamaji/values.yaml (1)
6-6: LGTM - Proper beta release updateThe Kamaji image update from v0.35.0-alpha.3 to v0.35.0-beta.1 with corresponding digest change is consistent with the release preparation objective.
packages/extra/bootbox/images/matchbox.tag (1)
1-1: LGTM - Consistent beta release migrationThe matchbox image update from v0.35.0-alpha.3 to v0.35.0-beta.1 with proper digest change aligns with the broader release preparation effort.
packages/system/cozystack-api/values.yaml (1)
2-2: LGTM - Final component updated for beta releaseThe cozystack-api image update to v0.35.0-beta.1 with corresponding digest change completes the consistent beta release preparation across components.
packages/system/objectstorage-controller/values.yaml (1)
3-3: No stale alpha references found; image bump approvedThe image tag and digest are correct, and a repository-wide search for
objectstorage-controller:.*alphareturned no matches.packages/system/cozystack-controller/values.yaml (1)
2-5: Controller image and version aligned to v0.35.0-beta.1
No remaining alpha references found in the repository. Approving these changes.packages/system/dashboard/values.yaml (1)
22-23: All alpha references removed; bump to v0.35.0-beta.1 approvedVerified repo-wide with a regex search for any remaining
v0.35.0-alpha.3references in both Dashboard and kubeapps-apis—no matches found. The image tags and digests are correctly specified for immutable deployments.
| "helmGlobalNamespace": {{ include "kubeapps.helmGlobalPackagingNamespace" . | quote }}, | ||
| "carvelGlobalNamespace": {{ .Values.kubeappsapis.pluginConfig.kappController.packages.v1alpha1.globalPackagingNamespace | quote }}, | ||
| "appVersion": "v0.35.0-alpha.3", | ||
| "appVersion": "v0.35.0-beta.1", |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Avoid drift: derive appVersion from the image version
Hardcoding appVersion risks divergence from the dashboard image tag. Use the same helper used for labels to compute it dynamically.
- "appVersion": "v0.35.0-beta.1",
+ "appVersion": {{ include "common.images.version" ( dict "imageRoot" .Values.dashboard.image "chart" .Chart ) | quote }},🏁 Script executed:
#!/bin/bash
# Check for any remaining alpha appVersion values in Kubeapps templates
rg -n --hidden --glob '!*node_modules/*' '"appVersion": *"v0\.35\.0-alpha\.3"'Length of output: 80
Let’s locate all hard-coded appVersion occurrences in the Kubeapps chart to confirm nothing slips through:
🏁 Script executed:
#!/bin/bash
# Search for any literal appVersion definitions in the Kubeapps chart templates
rg -n '"appVersion":' --hidden --glob '!*node_modules/*' packages/system/dashboard/charts/kubeapps/templatesLength of output: 228
Let’s verify that the common.images.version helper is defined in the Kubeapps chart:
🏁 Script executed:
#!/bin/bash
# Check for the common.images.version helper definition
rg -n 'define .*common\.images\.version' -n packages/system/dashboard/charts/kubeapps/templatesLength of output: 97
Let’s confirm that the common chart is a dependency and that its common.images.version helper is available:
🏁 Script executed:
#!/bin/bash
# Show the top of Chart.yaml to verify dependencies
sed -n '1,200p' packages/system/dashboard/charts/kubeapps/Chart.yaml
# List any vendored charts (dependencies)
find packages/system/dashboard/charts/kubeapps/charts -maxdepth 1 -type d
# Search for the helper definition in the common chart
rg -n 'define .*common\.images\.version' -n packages/system/dashboard/charts/kubeapps/charts/common/templates/_helpers.tplLength of output: 2438
Let’s locate the vendored Common chart and find where its common.images.version helper is defined:
🏁 Script executed:
#!/bin/bash
# List all files in the vendored common chart
find packages/system/dashboard/charts/kubeapps/charts/common -type f
# Inspect the top of the Common chart’s Chart.yaml for clues
sed -n '1,100p' packages/system/dashboard/charts/kubeapps/charts/common/Chart.yaml
# Search across the Common chart for the helper definition
rg -n 'define .*common\.images\.version' -n packages/system/dashboard/charts/kubeapps/charts/commonLength of output: 2984
Use dynamic helper for appVersion to prevent drift
The appVersion field in the ConfigMap is currently hard-coded, which may diverge from the actual dashboard image tag over time. Since the common.images.version helper is defined in the vendored Common chart, pull the version dynamically:
• File: packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml
Line: 79
Recommended diff:
- "appVersion": "v0.35.0-beta.1",
+ "appVersion": {{ include "common.images.version" (dict "imageRoot" .Values.dashboard.image "chart" .Chart) | quote }},📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "appVersion": "v0.35.0-beta.1", | |
| "appVersion": {{ include "common.images.version" (dict "imageRoot" .Values.dashboard.image "chart" .Chart) | quote }}, |
🤖 Prompt for AI Agents
In packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml
around line 79, the appVersion is hard-coded as "v0.35.0-beta.1" which can
drift; replace the literal with the vendored Common chart helper that returns
the image version (common.images.version) so the ConfigMap reads the dashboard
image version dynamically at template render time; update the template
expression to call that helper where appVersion is set, preserving string
quoting and YAML indentation so the rendered value matches the existing format.
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (2)
packages/apps/kubernetes/images/kubevirt-cloud-provider.tag (1)
1-1: Critical: Tag updated but digest unchanged - potential deployment issue.The image tag has been updated to 0.26.3, but the SHA256 digest appears to be the same as the previous version. This could indicate an issue with the image build or tagging process, potentially leading to deploying incorrect software versions.
packages/apps/clickhouse/images/clickhouse-backup.tag (1)
1-1: Critical: Version bump without digest change - potential deployment issue.The image tag has been updated from 0.11.1 to 0.12.0, but the SHA256 digest appears unchanged. This could indicate an issue with the image build process, potentially leading to deploying incorrect software versions.
🧹 Nitpick comments (1)
packages/system/cozystack-api/values.yaml (1)
2-2: LGTM. Pin to digest is good; consider consistent YAML quoting across files.Change looks correct. Optional: align quoting style for image strings across values files (some use quotes, some don’t).
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (20)
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/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(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)
🔇 Additional comments (18)
packages/system/kubevirt-csi-node/values.yaml (1)
3-3: LGTM! Proper image update with matching tag and digest changes.The kubevirt-csi-driver image has been correctly updated from 0.26.2 to 0.26.3 with a corresponding digest update, which is the expected behavior for image version bumps.
packages/system/dashboard/charts/kubeapps/templates/dashboard/configmap.yaml (1)
79-79: LGTM! Version bump aligns with beta release preparation.The appVersion has been correctly updated from v0.35.0-alpha.3 to v0.35.0-beta.1, which is consistent with the PR's objective to prepare the v0.35.0-beta.1 release.
packages/system/kubeovn-webhook/values.yaml (1)
3-3: LGTM! Proper beta release image update.The kubeovn-webhook image has been correctly updated from v0.35.0-alpha.3 to v0.35.0-beta.1 with a corresponding digest update, which aligns with the beta release preparation.
packages/extra/seaweedfs/images/objectstorage-sidecar.tag (1)
1-1: LGTM! Correct beta release image update.The objectstorage-sidecar image has been properly updated from v0.35.0-alpha.3 to v0.35.0-beta.1 with a corresponding digest update, which is consistent with the beta release preparation.
packages/system/kamaji/values.yaml (1)
6-6: LGTM! Proper kamaji image update for beta release.The kamaji image has been correctly updated from v0.35.0-alpha.3 to v0.35.0-beta.1 with a corresponding digest update, which is consistent with the beta release preparation.
packages/apps/http-cache/images/nginx-cache.tag (1)
1-1: LGTM! Valid digest update for same version.The digest has been updated while maintaining the same version tag (0.6.1), which is appropriate when image content changes (e.g., security patches, rebuilds) without bumping the version number.
packages/core/testing/values.yaml (1)
2-2: e2e-sandbox image reference verified – no alpha tags remainVerified that the only reference to the new sandbox image is in packages/core/testing/values.yaml (line 2) and there are no lingering v0.35.0-alpha tags in the testing configs. Everything looks good.
packages/system/objectstorage-controller/values.yaml (1)
3-3: Compatibility Confirmed: Controller and Sidecar on v0.35.0-beta.1
All references toobjectstorage-controllerandobjectstorage-sidecarhave been updated to v0.35.0-beta.1. No further changes required.packages/system/bucket/images/s3manager.tag (1)
1-1: Digest-only rotation for s3manager:v0.5.0Confirmed the updated digest is only referenced in packages/system/bucket/images/s3manager.tag – consistency is maintained across the repo. No code changes required here. You may still want to validate the new image’s supply chain/signature before deployment.
packages/system/seaweedfs/values.yaml (1)
119-119: ✅ Single Source of Truth Verified for COSI Sidecar ImageAll occurrences of the
ghcr.io/cozystack/cozystack/objectstorage-sidecarimage have been updated tov0.35.0-beta.1@sha256:ccc7ec31b2beebf09413b9a41ffa8fd06899510127572c9e1c1e30ddab45ebe9:• packages/system/seaweedfs/values.yaml:119
• packages/extra/seaweedfs/images/objectstorage-sidecar.tag:1No drift detected—digest matches in both locations.
packages/extra/bootbox/images/matchbox.tag (1)
1-1: Matchbox image bumped to beta: verifiedAll references now consume the updated tag file and no alpha references remain.
- Bootbox deployment (packages/extra/bootbox/templates/matchbox/deployment.yaml) uses
images/matchbox.tagrgsearch confirmed zero occurrences ofv0.35.0-alphapackages/core/installer/values.yaml (1)
2-2: Installer image bump to beta verified—no manual Chart.yaml version/appVersion updates needed.
- packages/core/installer/Chart.yaml (line 3) uses
version: 0.0.0as a build-time placeholder.- No
appVersionfield is defined in this chart.- No
v0.35.0-alphareferences found repository-wide.packages/system/cozystack-controller/values.yaml (2)
2-2: Controller image bump pinned to beta digest: OK.Change looks correct and consistent with the release train.
5-5: Version string usage verifiedI’ve confirmed that
cozystackVersionis consistently updated and consumed at runtime:• values.yaml (packages/system/cozystack-controller/values.yaml)
• Makefile yq command updating the tag (packages/system/cozystack-controller/Makefile)
• Deployment args passing--cozystack-version(templates/deployment.yaml line 23)
• Flag and telemetry field in main.go (cmd/cozystack-controller/main.go lines 87–107)No residual
-alphareferences found. All consumers expect the newv0.35.0-beta.1value.packages/apps/kubernetes/images/kubevirt-csi-driver.tag (1)
1-1: Pin consistency confirmed for kubevirt-csi-driverAll explicit references to
kubevirt-csi-driveracross the repo use
0.26.3@sha256:318ded0e7e2ca0329c86da13678699782bf5388cdcd074737c667872876f82fe.
No further updates are needed.packages/apps/kubernetes/images/cluster-autoscaler.tag (1)
1-1: Cluster-autoscaler image references updated
All occurrences of thecluster-autoscalerimage now use0.26.3@sha256:e4fbb7d2043f25b90cc8840468d0880e9d3d72ae8b1c8801bf8c35f944cc485d. No references to earlier tags or digests remain. LGTM.packages/system/kubeovn/values.yaml (1)
67-67: Chart supports digest embedded intagVerified that the Makefile sets
global.images.kubeovn.tagtov1.13.14@sha256:…and every Helm template uses onlyimage: {{ .Values.global.registry.address }}/{{ .Values.global.images.kubeovn.repository }}:{{ .Values.global.images.kubeovn.tag }}to render images as
<registry>/<repo>:<tag>@<digest>. Docker reference syntax allows a tag plus digest and there is no separatedigestfield in this chart. No duplicate kube-ovn digests were found elsewhere.packages/system/dashboard/values.yaml (1)
40-41: Dashboard & Kubeapps-APIs Beta Version Consistency VerifiedAll
v0.35.0-alpha.*references have been removed, and both the dashboard and kubeapps-apis images in packages/system/dashboard/values.yaml are pinned to v0.35.0-beta.1 with matching digests. No additional tags or digests remain in the chart templates.
| tag: v0.35.0-beta.1 | ||
| digest: "sha256:54906b3d2492c8603a347a5938b6db36e5ed5c4149111cae1804ac9110361947" |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Dashboard image pinned to beta.1; verify appVersion alignment.
The tag/digest bump looks good. Ensure the chart’s advertised appVersion is also set to v0.35.0-beta.1.
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Verify chart/config appVersion reflects v0.35.0-beta.1
echo "appVersion occurrences under dashboard chart:"
rg -n 'appVersion:\s*v0\.35\.0-beta\.1' packages/system/dashboard -S || true
# Show any other appVersion values (should be none for this chart)
echo
echo "Any other appVersion values:"
rg -n 'appVersion:\s*v0\.[0-9]+\.[0-9]+(-[a-z0-9\.\-]+)?' packages/system/dashboard -S || trueLength of output: 369
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Searching for Chart.yaml in packages/system/dashboard:"
fd Chart.yaml packages/system/dashboard || true
echo
echo "Listing any appVersion entries in Chart.yaml files under dashboard chart:"
CHART_FILES=$(fd Chart.yaml packages/system/dashboard || true)
if [[ -n "$CHART_FILES" ]]; then
echo "$CHART_FILES" | xargs -I{} grep -n 'appVersion:' {} || true
else
echo "No Chart.yaml found under packages/system/dashboard"
fiLength of output: 1768
Chart’s appVersion needs bump to v0.35.0-beta.1
The image tag/digest is updated, but the root Chart.yaml still advertises appVersion 2.12.0. Please update it to match the dashboard image:
• packages/system/dashboard/Chart.yaml:22
- Change
appVersion: 2.12.0
to
appVersion: v0.35.0-beta.1
🤖 Prompt for AI Agents
In packages/system/dashboard/Chart.yaml around line 22, update the root chart's
appVersion from "2.12.0" to "v0.35.0-beta.1" so it matches the dashboard image
tag/digest in values.yaml; edit the appVersion field only to the exact value
v0.35.0-beta.1.
2 participants
This PR prepares the release
v0.35.0-beta.1.Summary by CodeRabbit