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

[teutonet-bot]

Updates the ArtifactHUB images to the really deployed ones.

Summary by CodeRabbit

• Chores
  • Updated Docker image versions for Grafana Tempo, Memcached, and Grafana Alloy components in the Helm chart metadata annotations.

[coderabbitai]

Walkthrough

This change updates Docker image version strings for several components in the Helm chart annotations, including upgrades for Grafana Tempo, Memcached, and Grafana Alloy images. No logic, control flow, or exported entities were modified; only version metadata in the Helm chart was changed.

Changes

File(s)	Change Summary
charts/base-cluster/Chart.yaml	Updated Docker image versions for Grafana Tempo, Memcached, and Grafana Alloy in Helm chart annotations; added metrics-generator image annotation.

Possibly related PRs

• ci(base-cluster/artifacthub-images): Update ArtifactHUB images #1574: Updates container image version strings in the same Helm chart annotations.
• ci(base-cluster/artifacthub-images): Update ArtifactHUB images #1535: Updates image versions in the annotations of the same Helm chart file.
• chore(base-cluster): pin all versions #1447: Updates container image versions in Helm chart metadata for the base-cluster.

Suggested labels

base-cluster

Suggested reviewers

• tasches
• cwrau
• marvinWolff
• github-actions

Poem

A hop and a skip, new versions appear,
Grafana and Memcached, all brought up to cheer.
Alloy shines brighter, Tempo runs fast,
With version bumps gentle, our clusters will last.
🐰✨

---

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 (3)

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

28-33: Consider pinning the new Tempo tags to immutable digests

The six updated bitnami/grafana-tempo:2.8.1-debian-12-r1 entries are still tag-only references, whereas many other images in the list are pinned with @sha256: digests.
A digest lock prevents accidental pulls of a mutated tag and keeps the SBOM on ArtifactHUB reproducible.

-    - image: docker.io/bitnami/grafana-tempo:2.8.1-debian-12-r1
+    - image: docker.io/bitnami/grafana-tempo:2.8.1-debian-12-r1@sha256:<tempo-digest>

Same applies to lines 29-33.
If you need the digest values I can script-fetch them.

---

40-40: Memcached bump LGTM, but digest consistency would help

bitnami/memcached:1.6.38-debian-12-r4 is a straight patch release; no breaking changes expected.
For the same reproducibility reasons mentioned above, consider pinning it to a digest.

---

24-85: Long-term maintainability: generate this list instead of manual edits

Manually curating ~60 image lines is error-prone and easy to fall out of sync (as seen with the missing metrics-generator earlier).
Consider:

1. A post-render script that extracts images from the rendered manifests (yq e '.spec.template.spec.containers[].image') and rewrites Chart.yaml before commit.
2. Or a CI guard that diff-checks the list against the rendered output and fails if they diverge.

This keeps ArtifactHUB data accurate without manual toil.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 63c2593 and ded2c2a.

📒 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). (4)

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

🔇 Additional comments (2)

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

28-33: Nice catch adding the metrics-generator entry

The list previously omitted the grafana-tempo-metrics-generator StatefulSet, which could confuse ArtifactHUB’s image scanner. The new line 33 fixes the gap.

---

52-52: Alloy upgrade OK – watch for config deprecations

grafana/alloy jumped from v1.7.5 → v1.9.2. The Alloy release notes mention config-field renames (batch_size → max_batch_size, etc.). Double-check the Helm values rendered for telemetry-collector to avoid runtime errors.

[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]({"errors": ["Missing required field 'content'"]})

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 2551194 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