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.
29 lines
701 B
YAML
29 lines
701 B
YAML
apiVersion: argoproj.io/v1alpha1
|
|
kind: Application
|
|
metadata:
|
|
name: envoy-gateway
|
|
namespace: argocd
|
|
annotations:
|
|
argocd.argoproj.io/sync-wave: "2"
|
|
spec:
|
|
project: default
|
|
sources:
|
|
- repoURL: docker.io/envoyproxy
|
|
chart: gateway-helm
|
|
targetRevision: "v1.7.1"
|
|
helm:
|
|
valueFiles:
|
|
- $values/manifests/envoy-gateway/values.yaml
|
|
- repoURL: https://gitea.fireflylab.cc/duynguyen/cluster-bootstrap.git
|
|
targetRevision: main
|
|
ref: values
|
|
destination:
|
|
server: https://kubernetes.default.svc
|
|
namespace: envoy-gateway-system
|
|
syncPolicy:
|
|
automated:
|
|
prune: true
|
|
selfHeal: true
|
|
syncOptions:
|
|
- CreateNamespace=true
|