Skip to content

feat: integrate ArgoInit as gitops engine in ClusterProfile#49

Merged
patrick-hermann-sva merged 1 commit intomainfrom
feat/argocd-gitops-engine
Apr 1, 2026
Merged

feat: integrate ArgoInit as gitops engine in ClusterProfile#49
patrick-hermann-sva merged 1 commit intomainfrom
feat/argocd-gitops-engine

Conversation

@patrick-hermann-sva
Copy link
Copy Markdown
Contributor

Summary

  • Add argocd spec section to XRD (namespace, chart, repositories)
  • Emit ArgoInit XR when gitops.engine: argocd, gated on Cilium readiness
  • Auto-derive k8sServiceHost from RemoteCluster kindClusterName (provider-kubeconfig v0.11.7+)
  • Simplify kind example CR (no cilium.clusterName needed)
  • Update README with ArgoCD examples, pipeline tables, prerequisites

Test plan

  • Deployed composition on dev cluster — existing engine: none profile unaffected
  • XRD schema validates with argocd spec section
  • Test gitops.engine: argocd on a target cluster

🤖 Generated with Claude Code

- Add argocd spec section to XRD (namespace, chart, repositories)
- Emit ArgoInit XR when gitops.engine=argocd, gated on Cilium readiness
- Add Usage for ArgoInit → Cilium deletion ordering
- Read ArgoInit readiness in status step (was hardcoded False)
- Auto-derive k8sServiceHost from RemoteCluster kindClusterName
- Simplify kind example (no cilium.clusterName needed)
- Update README with ArgoCD examples, pipeline tables, prerequisites

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@patrick-hermann-sva patrick-hermann-sva merged commit 8fe5ad0 into main Apr 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant