fix: register envoy-gateway OCI repo declaratively in argocd values

ArgoCD only builds a helm-pull command for oci:// sources when the repo is
registered with enableOCI: true; otherwise it falls back to classic --repo
handling, which errors on an oci:// URL. Registered via configs.repositories
in argocd's own values.yaml (Git-managed), Application source updated to
the bare host/path form ArgoCD expects for OCI repos.
This commit is contained in:
2026-07-21 12:02:02 +07:00
parent 2a07b6decf
commit fef69d587f
2 changed files with 7 additions and 1 deletions

View File

@@ -8,7 +8,7 @@ metadata:
spec: spec:
project: default project: default
sources: sources:
- repoURL: oci://docker.io/envoyproxy - repoURL: docker.io/envoyproxy
chart: gateway-helm chart: gateway-helm
targetRevision: "v1.7.1" targetRevision: "v1.7.1"
helm: helm:

View File

@@ -18,6 +18,12 @@ global:
configs: configs:
params: params:
server.insecure: true # TLS terminated at Envoy Gateway server.insecure: true # TLS terminated at Envoy Gateway
repositories:
envoy-gateway-oci:
url: docker.io/envoyproxy
name: envoy-gateway-oci
type: helm
enableOCI: "true"
server: server:
replicas: 1 replicas: 1