Adopting teams destination based provisioning

This commit is contained in:
2026-09-29 11:57:16 +01:00
parent 06e0ab0fb3
commit b1fa450372
2 changed files with 14 additions and 9 deletions

View File

@@ -1,17 +1,20 @@
# Lives on the HUB, in the agent's namespace. The argocd-agent pushes it to the spoke.
# Lives on the HUB, in team demo's namespace. Destination-based mapping routes it to the spoke named
# by destination.name, where it keeps this namespace (team-demo) rather than moving to argocd.
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: demo-vivek-11
namespace: apps-lab
namespace: team-demo
spec:
project: apps-lab
# Created by the platform (argocd-principal teams). Allows deploying only to demo-* on the spoke.
project: team-demo
source:
repoURL: https://gitea.kyndemo.live/validate/demo-vivek-11.git
targetRevision: main
path: deploy/manifests
destination:
# name, never server: server https://kubernetes.default.svc resolves to the hub itself.
# The agent to deploy to -- under destination-based mapping this IS the routing key. Never
# server: https://kubernetes.default.svc resolves to the hub itself.
name: apps-lab
namespace: demo-vivek-11
syncPolicy: