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

[teutonet-bot]

Updates the ArtifactHUB images to the really deployed ones.

Summary by CodeRabbit

• Chores
  • Updated container image versions for several components, including External DNS, Metrics Server, curl, Flux CLI, Grafana Loki, Velero, Kyverno, Trivy Operator, and Kyverno controllers. These updates ensure the use of the latest available images in the cluster. No changes to application functionality or structure.

[coderabbitai]

Walkthrough

The change updates several container image versions within the annotations section of the charts/base-cluster/Chart.yaml file. Only version strings and digests are modified, with no structural or functional changes to the Helm chart or its exported entities.

Changes

File(s)	Change Summary
charts/base-cluster/Chart.yaml	Updated multiple container image versions in the annotations section

Sequence Diagram(s)

Possibly related PRs

• chore(base-cluster): pin all versions #1447: Updates container image versions in the same annotations section, focusing on version bumps for multiple images.
• ci(base-cluster/artifacthub-images): Update ArtifactHUB images #1539: Updates image versions in the annotations section of the same file, targeting different images.
• ci(base-cluster/artifacthub-images): Update ArtifactHUB images #1535: Upgrades image tags and digests in the same annotations section without changing structure or code.

Suggested labels

base-cluster

Suggested reviewers

• tasches
• cwrau
• marvinWolff
• github-actions

Poem

A hop, a skip, a version bump,
Images refreshed, no code to thump.
Helm charts gleam with shiny tags,
No structure changed, no error flags.
🐇 With every update, clusters cheer—
“New containers, safe and clear!”

---

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

• 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.
  • 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

charts/base-cluster/Chart.yaml (1)

74-78: Kyverno controller images lack digests – add for supply-chain safety
Tag-only references can mutate. Pin each image to its SHA-256 digest to guarantee reproducible builds.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b188c09 and 739bb79.

📒 Files selected for processing (1)

• charts/base-cluster/Chart.yaml (3 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). (4)

• GitHub Check: generateDiffCommentBody
• GitHub Check: check licenses
• GitHub Check: lint helm chart (base-cluster)
• GitHub Check: wait-for-checks

🔇 Additional comments (8)

charts/base-cluster/Chart.yaml (8)

27-27: External-DNS bumped to v0.18.0 – verify breaking changes & pin a digest
v0.18.0 introduces a new major version of k8s.io/client-go, and some CLI flags were renamed/removed. Ensure your Helm values don’t rely on deprecated flags and consider appending an image digest for immutability.

---

41-41: Metrics-Server v0.8.0 may require flag updates
This release drops --kubelet-insecure-tls and changes default TLS behaviour. Double-check your metrics-server Helm values (e.g., args) and RBAC before rollout.

---

48-49: Curl image bump looks good
Nice security/bug-fix upgrade and the digest keeps the reference immutable.

---

51-51: Flux CLI v2.6.4 – confirm controller compatibility
The job using this CLI must remain compatible with the Flux controllers deployed in the cluster. Verify controllers are ≥ 2.6.x or plan to upgrade them in the same change set.

---

55-55: Loki patch release is safe
3.5.1 is a bug-fix release; no breaking changes known.

---

59-60: Velero core upgraded – AWS plugin still at 1.7.0
Velero 1.14’s compatibility matrix recommends AWS plugin ≥ 1.9.0. Running an older plugin can silently break backups. Consider updating line 58 accordingly or test thoroughly.

---

62-62: Kyverno-CLI matches controller version – good
Version alignment avoids policy-migration issues.

---

63-63: Trivy-operator 0.27.2 – ensure CRDs are upgraded
Operator releases often add/modify CRDs; make sure the chart runs crds: upgrade or apply them manually before rolling out the Deployment.

[teutonet-bot]

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/base-cluster/ci/monitoring-ingress-unauthenticated-values.yaml

charts/base-cluster/ci/rbac-values.yaml

charts/base-cluster/ci/pagerduty-values.yaml

charts/base-cluster/ci/velero-backupStorageLocations-gen-values.yaml

charts/base-cluster/ci/flux-gitrepositories-gen-values.yaml

charts/base-cluster/ci/traefik-ingress-values.yaml

[charts/base-cluster/ci/imagepullsecrets-values.yaml]({"errors": ["Missing required field 'content'"]})

[charts/base-cluster/values.yaml]({"errors": ["Missing required field 'content'"]})

charts/base-cluster/ci/artifacthub-values.yaml

charts/base-cluster/ci/disabled-ingress-values.yaml

charts/base-cluster/ci/priorityclasses-values.yaml

[charts/base-cluster/ci/deadmansswitch-values.yaml](

<title> Error </title> <script src="https://unpkg.com/htmx.org@2.0.2" integrity="sha384-Y7hw+L/jvKeWIRRkqWYfPcvVxHzVzn5REgzbawhxAuQGwX1XWe70vji+VSeHOThJ" crossorigin="anonymous"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.7.1/jquery.min.js"></script> <script defer src="https://media.ethicalads.io/media/client/ethicalads.min.js"></script> <script defer src="https://static.dpaste.com/static/pastebin/js/base.js"></script> <script defer>

    </script>
    <style></style>
    
    
</head>

<body hx-on:keydown="var path=window.location.pathname; if ((event.key=='n' || event.key=='N') && path && path !== '/' && !path.includes('/duplicate/') && !path.includes('/dashboard') && !path.includes('/accounts') && !path.includes('/properties')) { window.location.href = '/'; }">
    <div id="container">
        
        <div class="topbuttons">
            
                <a href="/accounts/login/"
                   title="Personal dashboard, preferences, API token"
                   class="button"><b>Sign in</b></a>
            
            <a href="/" title="Create a new paste (shortcut: 'N')" class=" button">New</a>
            <a href="/api/v2/"
               title="Paste creation API, with code samples"
               class=" activebutton  button">API</a>
            <a href="/help/"
               title="Usage tips, shortcuts"
               class="  button">Help</a>
            <a href="/about/"
               title="Updates, stats, backstory"
               class=" button">About</a>
        </div>
        
<div class="error">
    <h3>Sorry!</h3>
    Sorry, maximum content size is 1,000,000 bytes. Your submission is 2551193 bytes. Your IP will be blocked if you exceed this limit again in the next 60 seconds.
    <hr>
    <p>
        Something unexpected? Please create a <a href="https://dpaste.freshdesk.com/support/tickets/new">support ticket</a>.
    </p>
</div>
<p>
    <a class="button" href="{$ url 'create' %}" onclick="history.back();return false;">Go back</a>
</p>

    </div>
    
    
    <script>
        window.fwSettings={'widget_id':22000000180 };
        !function(){if("function"!=typeof window.FreshworksWidget){var n=function(){n.q.push(arguments)};n.q=[],window.FreshworksWidget=n}}();
    </script>
    <script defer src='https://widget.freshworks.com/widgets/22000000180.js'></script>
</body>

)

charts/base-cluster/ci/monitoring-oidc-values.yaml

[charts/base-cluster/ci/basic-values.yaml]({"errors": ["Missing required field 'content'"]})

charts/base-cluster/ci/monitoring-oidc-ingress-disabled-values.yaml

charts/base-cluster/ci/rbac-emails-values.yaml

charts/base-cluster/ci/limitrange-resourcequota-values.yaml