fix(container): update image mirror.gcr.io/prompp/prompp (0.8.2 → 0.8.3)

[smurf-bot]

This PR contains the following updates:

Package	Update	Change
mirror.gcr.io/prompp/prompp	patch	0.8.2 → 0.8.3

---

Configuration

📅 Schedule: (in timezone America/Edmonton)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[smurf-bot]

konflate — summary

Note

+0 added · 2 changed · −0 removed — 2 resources · 2 apps

Tip

Routine — only container-image and chart-version changes; nothing else changed.

Image changes

image	from	to
mirror.gcr.io/prompp/prompp	0.8.2	0.8.3

View the full rendered diff →

_{konflate · rendered fbec7ab · advisory, not a gate}

[its-saffron]

AI Automated Review

Analysis engine: MiniMax-M2.7@https://litellm.jory.dev/v1 (anthropic) — escalated (fast_low_confidence)

Approve — routine patch release for mirror.gcr.io/prompp/prompp (0.8.2 → 0.8.3), a Prometheus Operator-sidecar image used in the kube-prometheus-stack HelmRelease.

Change Summary

File	Change
kubernetes/apps/base/observability/kube-prometheus-stack/helmrelease.yaml	tag: 0.8.2 → tag: 0.8.3

Konflate confirms only the image tag changed in the rendered manifest (mirror.gcr.io/prompp/prompp:0.8.2 → mirror.gcr.io/prompp/prompp:0.8.3); 0 added, 2 changed, 0 removed resources.

Required Checks — Explicit Results

✓ Validate manifest against target cluster version

This PR does not touch Kubernetes API versions, Helm chart version, or any cluster-level API. The HelmRelease structure is unchanged — only the container image tag. The manifest is valid YAML with the correct helm.toolkit.fluxcd.io/v2 schema, uses spec.chartRef with a pinned OCIRepository, and has spec.interval: 15m. The prompp image is an override for the Prometheus Operator's sidecar; it does not interact with the kubelet or node OS. No Talos or Kubernetes version compatibility concern applies here.

✓ Check for resource quota / limit changes

No resource requests or limits are modified. The existing prometheusSpec.resources block (requests.cpu: 100m, limits.memory: 3000Mi) is untouched — confirmed by both the raw diff and konflate's rendered diff.

Standards Compliance

• HelmRelease via Flux: ✓ spec.chartRef + OCIRepository, no raw manifests
• Container registry: mirror.gcr.io is the Google Container Registry mirror (allowlisted)
• Namespace absent: ✓ Intentional per AGENTS.md — injected by kustomize
• OCI artifact pinning: N/A — this is a container image, not a Helm chart OCI artifact

Evidence Provider Findings

• konflate: Routine change — only image tag updated; no data-loss, RBAC, or immutable-field cautions
• upgrade-impact: Upstream release notes for prompp/prompp 0.8.2 → 0.8.3 were not retrievable; this is a known blind spot but patch releases carry minimal risk, and CI image-pull checks passed for both main and utility clusters
• CI: All checks succeeded (Image Pull × 5, Konflate, AI PR Review)

Unknowns / Needs Verification

• Upstream changelog: Could not retrieve release notes for prompp/prompp 0.8.3. The change is a patch-level bump (0.8.2 → 0.8.3) with CI image-pull validation passing on both target clusters, so this is a non-blocking caveat.