fix(velero): repoint CRD-hook kubectl image off the removed bitnami mirror

The velero chart's pre-install `velero-upgrade-crds` hook defaults its kubectl
image to docker.io/bitnami/kubectl, whose public Docker Hub catalog Bitnami
removed (Aug 2025). `docker.io/bitnami/kubectl:1.31` now 404s, leaving the hook
job in Init:ImagePullBackOff so Velero never installs (no Deployment,
node-agent, or BackupStorageLocation).

Set kubectl.image to the Rancher-maintained mirror docker.io/rancher/kubectl,
pinned to the cluster's exact k8s minor v1.31.5 (multi-arch amd64/arm64,
verified pullable via the Docker Hub registry API). All other Velero values
(BSL → versitygw s3://velero, kopia FSB node-agent, the two Schedules, the
velero-cloud-credentials secret) are unchanged.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
This commit is contained in:
jakman85andClaude Opus 4.8 committed 2026-08-29 11:01:17 -05:00
1 parent b5d65e9bc8
commit 8fdd2a3f60
1 file changed
+9
+9
View File
@@ -40,6 +40,15 @@ spec:
remediation:
retries: 3
values:
# --- CRD upgrade/cleanup hook image. The chart default is docker.io/bitnami/kubectl, whose public
# Docker Hub catalog Bitnami REMOVED (Aug 2025) — `docker.io/bitnami/kubectl:1.31` 404s, leaving
# the pre-install `velero-upgrade-crds` hook in Init:ImagePullBackOff and Velero never installing.
# Repoint to the Rancher-maintained kubectl mirror, pinned to the cluster's exact k8s minor
# (v1.31.5, multi-arch amd64/arm64). Verified pullable via the Docker Hub registry API. ---
kubectl:
image:
repository: docker.io/rancher/kubectl
tag: v1.31.5
# --- AWS object-store plugin (BSL provider=aws → MinIO S3-compatible), loaded as an init container.
# Image minor MUST track the Velero minor (chart 8.x = Velero 1.15 → plugin v1.11.x). ---
initContainers: