Skip to content

ci(base-cluster/artifacthub-images): Update ArtifactHUB images#1587

Merged
teutonet-bot merged 0 commit intomainfrom
ci/base-cluster/update-artifacthub-images
Jul 23, 2025
Merged

ci(base-cluster/artifacthub-images): Update ArtifactHUB images#1587
teutonet-bot merged 0 commit intomainfrom
ci/base-cluster/update-artifacthub-images

Conversation

@teutonet-bot
Copy link
Copy Markdown
Contributor

@teutonet-bot teutonet-bot commented Jul 18, 2025

Updates the ArtifactHUB images to the really deployed ones.

Summary by CodeRabbit

  • Chores
    • Updated multiple container image versions in chart metadata to reflect the latest available releases. No changes to application functionality or structure.

github-actions[bot]
github-actions Bot previously approved these changes Jul 18, 2025
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jul 18, 2025

Walkthrough

This change updates the container image versions listed in the artifacthub.io/images annotation within the charts/base-cluster/Chart.yaml file. The updates include version increments and digest revisions for multiple Bitnami, Grafana, Prometheus, Traefik, and other container images. No functional or structural code changes were made.

Changes

File(s) Change Summary
charts/base-cluster/Chart.yaml Updated image versions and digests in the artifacthub.io/images annotation for Bitnami, Grafana, Prometheus, Traefik, and other container images.

Possibly related PRs

Suggested labels

base-cluster

Suggested reviewers

  • tasches
  • cwrau
  • marvinWolff
  • github-actions

Poem

In the garden of charts where images bloom,
New versions arise, dispelling old gloom.
A hop and a skip, with tags freshly spun,
The cluster is ready—its updates begun!
🐇✨


📜 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 23a605e and 82db2ab.

📒 Files selected for processing (1)
  • charts/base-cluster/Chart.yaml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • charts/base-cluster/Chart.yaml
⏰ 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). (3)
  • GitHub Check: check licenses
  • GitHub Check: lint helm chart (base-cluster)
  • GitHub Check: wait-for-checks

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
charts/base-cluster/Chart.yaml (1)

28-33: Grafana-Tempo lines: multiple duplicates – no issues, but consider deduplication
Six identical lines keep the 1-to-1 mapping to each workload, which is fine for ArtifactHUB reporting. If you want to shrink the annotation block, you could drop the duplicates without affecting functionality.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c29757a and 578ec79.

📒 Files selected for processing (1)
  • charts/base-cluster/Chart.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). (3)
  • GitHub Check: check licenses
  • GitHub Check: lint helm chart (base-cluster)
  • GitHub Check: wait-for-checks
🔇 Additional comments (3)
charts/base-cluster/Chart.yaml (3)

27-27: External-DNS image bump LGTM
The tag jump to 0.18.0-debian-12-r1 is only a patch update; no breaking CLI flag changes were introduced between 0.17 → 0.18.


41-41: Metrics-server 0.8.0: verify API flag set compatibility
v0.8 switches the default preferred address types; if your Helm values still set the --kubelet-insecure-tls flag, behaviour is unchanged, otherwise the new defaults might block metrics collection on clusters with custom network setups.


63-63: Trivy-operator patch bump looks safe
0.27.3 only contains CVE database refreshes; no CRD/schema changes.

Comment on lines +38 to +39
- image: docker.io/bitnami/kubectl:1.33.3-debian-12-r1@sha256:cd354d5b25562b195b277125439c23e4046902d7f1abc0dc3c75aad04d298c17 # default/Job/flux-generate-gpg-key-secret-main.yaml
- image: docker.io/bitnami/kubectl:1.33.3-debian-12-r1@sha256:cd354d5b25562b195b277125439c23e4046902d7f1abc0dc3c75aad04d298c17 # default/Job/prevent-uninstallation.yaml
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

kubectl version drift within the same chart
You now list 1.33.3 for two jobs, but three earlier jobs (lines 34-36) are still at 1.32.3. Keeping a single minor version across all helper Jobs avoids subtly different behaviour (e.g. changed default server-side dry-run semantics in v1.33).

Diff suggestion to align everything to 1.33.3:

-    - image: docker.io/bitnami/kubectl:1.32.3                                                                                          #  kyverno/HelmRelease/kyverno/kyverno/Job/kyverno-clean-reports.yaml
-    - image: docker.io/bitnami/kubectl:1.32.3                                                                                          #  kyverno/HelmRelease/kyverno/kyverno/Job/kyverno-remove-configmap.yaml
-    - image: docker.io/bitnami/kubectl:1.32.3                                                                                          #  kyverno/HelmRelease/kyverno/kyverno/Job/kyverno-scale-to-zero.yaml
+    - image: docker.io/bitnami/kubectl:1.33.3-debian-12-r1                                                                             #  kyverno/HelmRelease/kyverno/kyverno/Job/kyverno-clean-reports.yaml
+    - image: docker.io/bitnami/kubectl:1.33.3-debian-12-r1                                                                             #  kyverno/HelmRelease/kyverno/kyverno/Job/kyverno-remove-configmap.yaml
+    - image: docker.io/bitnami/kubectl:1.33.3-debian-12-r1                                                                             #  kyverno/HelmRelease/kyverno/kyverno/Job/kyverno-scale-to-zero.yaml
📝 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.

Suggested change
- image: docker.io/bitnami/kubectl:1.33.3-debian-12-r1@sha256:cd354d5b25562b195b277125439c23e4046902d7f1abc0dc3c75aad04d298c17 # default/Job/flux-generate-gpg-key-secret-main.yaml
- image: docker.io/bitnami/kubectl:1.33.3-debian-12-r1@sha256:cd354d5b25562b195b277125439c23e4046902d7f1abc0dc3c75aad04d298c17 # default/Job/prevent-uninstallation.yaml
- image: docker.io/bitnami/kubectl:1.33.3-debian-12-r1 # kyverno/HelmRelease/kyverno/kyverno/Job/kyverno-clean-reports.yaml
- image: docker.io/bitnami/kubectl:1.33.3-debian-12-r1 # kyverno/HelmRelease/kyverno/kyverno/Job/kyverno-remove-configmap.yaml
- image: docker.io/bitnami/kubectl:1.33.3-debian-12-r1 # kyverno/HelmRelease/kyverno/kyverno/Job/kyverno-scale-to-zero.yaml
🤖 Prompt for AI Agents
In charts/base-cluster/Chart.yaml around lines 34 to 39, the kubectl image
versions are inconsistent, with some jobs using version 1.32.3 and others
1.33.3. To fix this, update the image tags for all kubectl jobs to use the same
minor version, specifically 1.33.3, ensuring uniform behavior across all jobs by
replacing the 1.32.3 versions with 1.33.3.

github-actions[bot]
github-actions Bot previously approved these changes Jul 21, 2025
auto-merge was automatically disabled July 23, 2025 01:26

Pull request was closed

@teutonet-bot teutonet-bot force-pushed the ci/base-cluster/update-artifacthub-images branch from 82db2ab to 7b29989 Compare July 23, 2025 01:26
@teutonet-bot teutonet-bot merged commit 7b29989 into main Jul 23, 2025
24 of 25 checks passed
@teutonet-bot teutonet-bot deleted the ci/base-cluster/update-artifacthub-images branch July 23, 2025 01:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant