Prepare release v0.23.1

[kvaps]

Signed-off-by: Andrei Kvapil [email protected]

Summary by CodeRabbit

• Image Updates

  • Updated Cozystack installer to version v0.23.1
  • Updated multiple application images with new digests, including:
    • ClickHouse backup
    • Postgres backup
    • Nginx cache
    • Cluster autoscaler
    • KubeVirt components
    • S3 manager
    • Dashboard
    • Kamaji
    • KubeOVN

• Version Bumps

  • Incremented Cozystack core components to v0.23.1

[coderabbitai]

Walkthrough

This pull request involves a comprehensive update of image versions and digests across multiple components of the Cozystack platform. The primary focus is on upgrading the version from v0.23.0 to v0.23.1 for various system and application components, including the core Cozystack installer, API, controller, dashboard, and several application-specific images.

Changes

File/Path	Change Summary
manifests/cozystack-installer.yaml	Updated cozystack and darkhttpd container images from v0.23.0 to v0.23.1
packages/core/installer/values.yaml	Updated Cozystack image version and digest
packages/system/cozystack-api/values.yaml	Updated Cozystack API image version and digest
packages/system/cozystack-controller/values.yaml	Updated Cozystack controller image version and digest
packages/system/dashboard/values.yaml	Updated dashboard and kubeappsapis image tags and digests
Multiple image tag files	Updated image digests for various components like clickhouse-backup, postgres-backup, nginx-cache, cluster-autoscaler, etc.

Possibly related PRs

• Prepare release v0.23.0 #591: Previous version upgrade from v0.22.0 to v0.23.0

Suggested labels

enhancement

Poem

🐰 Hop, hop, version update time!
Cozystack leaps to version sublime
Images tagged with care so neat
From v0.23.0 to v0.23.1, what a treat!
Containers dancing, digests align
Smooth as a rabbit's whisker, simply divine! 🚀

---

📜 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 fb723bc and 3dc1a02.

📒 Files selected for processing (20)

• manifests/cozystack-installer.yaml (2 hunks)
• packages/apps/clickhouse/images/clickhouse-backup.tag (1 hunks)
• packages/apps/ferretdb/images/postgres-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/apps/postgres/images/postgres-backup.tag (1 hunks)
• packages/core/installer/values.yaml (1 hunks)
• packages/core/testing/values.yaml (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/charts/kubeapps/templates/dashboard/configmap.yaml (1 hunks)
• packages/system/dashboard/values.yaml (1 hunks)
• packages/system/kamaji/values.yaml (1 hunks)
• packages/system/kubeovn/values.yaml (1 hunks)

✅ Files skipped from review due to trivial changes (17)

• packages/apps/mysql/images/mariadb-backup.tag
• packages/apps/http-cache/images/nginx-cache.tag
• packages/apps/kubernetes/images/kubevirt-csi-driver.tag
• packages/apps/postgres/images/postgres-backup.tag
• packages/system/kamaji/values.yaml
• packages/apps/clickhouse/images/clickhouse-backup.tag
• packages/apps/kubernetes/images/kubevirt-cloud-provider.tag
• packages/apps/ferretdb/images/postgres-backup.tag
• packages/system/bucket/images/s3manager.tag
• packages/system/cozystack-api/values.yaml
• packages/system/kubeovn/values.yaml
• packages/apps/kubernetes/images/cluster-autoscaler.tag
• packages/apps/kubernetes/images/ubuntu-container-disk.tag
• packages/system/cozystack-controller/values.yaml
• packages/core/installer/values.yaml
• packages/core/testing/values.yaml
• packages/system/dashboard/values.yaml

🔇 Additional comments (3)

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

16-16: Verify the new Cilium image digest.

Let's ensure the new digest corresponds to the correct image tag and check for any security advisories.

✅ Verification successful

✓ Verified: New Cilium image digest is valid

The new digest sha256:eae9d5531c115... is confirmed to exist in the container registry for tag 1.16.5, representing a legitimate update of the image.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the Cilium image digest and check for security advisories

# Check if the image exists and verify its digest
REPO="ghcr.io/aenix-io/cozystack/cilium"
TAG="1.16.5"
EXPECTED_DIGEST="sha256:eae9d5531c115f8946990a731bfaaebc905b020a2957559b3c9f2ce1c655a834"

# Get the image manifest and verify the digest
gh api \
  -H "Accept: application/vnd.oci.image.index.v1+json" \
  "/users/aenix-io/packages/container/cozystack%2Fcilium/versions" \
  --jq ".[] | select(.metadata.container.tags[] == \"${TAG}\") | .name"

# Check for any security advisories for Cilium
gh api graphql -f query='
{
  securityVulnerabilities(first: 5, ecosystem: CONTAINER, package: "cilium") {
    nodes {
      advisory {
        summary
        severity
        publishedAt
      }
      vulnerableVersionRange
      firstPatchedVersion {
        identifier
      }
    }
  }
}'

Length of output: 1424

---

Script:

#!/bin/bash
# Try different approaches to verify the Cilium image

# 1. Check the package in GitHub Container Registry
gh api \
  -H "Accept: application/json" \
  "/users/aenix-io/packages/container/cozystack%2Fcilium/versions" | jq -r '.[] | select(.metadata.container.tags | contains(["1.16.5"])) | .name'

# 2. Check Cilium's official repository tags
gh api \
  -H "Accept: application/json" \
  "/orgs/cilium/packages/container/cilium/versions" | jq -r '.[] | select(.metadata.container.tags | contains(["1.16.5"])) | .name'

# 3. Check for security advisories with correct ecosystem
gh api graphql -f query='
{
  securityVulnerabilities(first: 5, ecosystem: CONTAINER_LINUX, package: "cilium") {
    nodes {
      advisory {
        summary
        severity
        publishedAt
      }
      vulnerableVersionRange
      firstPatchedVersion {
        identifier
      }
    }
  }
}'

Length of output: 1292

manifests/cozystack-installer.yaml (1)

71-71: Version update looks consistent with release v0.23.1.

The image version updates for both containers align with the PR objective.

Also applies to: 90-90

✅ Verification successful

Image verification successful and container configuration is correct

The cozystack image v0.23.1 exists in the registry and contains the darkhttpd binary, making it suitable for both containers' use cases.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the cozystack image and its usage

# Check if the image exists in the registry
REPO="ghcr.io/aenix-io/cozystack/cozystack"
TAG="v0.23.1"

gh api \
  -H "Accept: application/vnd.oci.image.index.v1+json" \
  "/users/aenix-io/packages/container/cozystack%2Fcozystack/versions" \
  --jq ".[] | select(.metadata.container.tags[] == \"${TAG}\") | .name"

# Verify that darkhttpd binary exists in the image
# This is important since both containers use the same image
rg -l "darkhttpd" | grep -i "dockerfile"

Length of output: 651

---

Script:

#!/bin/bash
# Description: Verify the cozystack image and its usage with correct headers

# Check if the image exists in the registry
gh api \
  -H "Accept: application/json" \
  "/users/aenix-io/packages/container/cozystack%2Fcozystack/versions" \
  --jq ".[] | select(.metadata.container.tags[] == \"v0.23.1\") | .name"

# Check Dockerfile content
cat packages/core/installer/images/cozystack/Dockerfile

Length of output: 1802

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

79-79: Version update in dashboard config aligns with release.

The appVersion update to v0.23.1 is consistent with the overall release version.

✅ Verification successful

Version consistency verified across dashboard components

The appVersion v0.23.1 in the dashboard configmap is consistent with the image tags defined in values.yaml.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version consistency across dashboard components

# Check for any other version references in dashboard configs
rg -l "v0\.23\.[0-9]" packages/system/dashboard/

# Check if the dashboard image tag matches the appVersion
rg "tag:" packages/system/dashboard/values.yaml

Length of output: 251

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.