k8s.io icon indicating copy to clipboard operation
k8s.io copied to clipboard

eks-prow-build-cluster: Replace FluxCD with ArgoCD

Open xmudrii opened this issue 1 year ago • 5 comments

It has been discussed to replace FluxCD that we use for eks-prow-build-cluster with ArgoCD. ArgoCD offers many more features that can help us to easier manage all our clusters (e.g. UI, terminal/console, easier to debug issues...).

### Tasks
- [ ] Investigate what does it take to replace FluxCD with ArgoCD and come up with a proposal
- [ ] Investigate multi-cluster setup for ArgoCD (e.g. so that we can manage both GKE and EKS clusters with it)
- [ ] Set up a new cluster to host ArgoCD and the monitoring stack
- [ ] Deploy ArgoCD
- [ ] Migrate eks-prow-build-cluster from FluxCD to ArgoCD

/assign @xmudrii @koksay /sig k8s-infra /area infra infra/aws /milestone v1.30 /priority important-soon

xmudrii avatar Feb 19 '24 17:02 xmudrii

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar May 19 '24 18:05 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar May 20 '24 12:05 xmudrii

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Aug 18 '24 13:08 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Aug 19 '24 10:08 xmudrii

/unassign

xmudrii avatar Aug 27 '24 13:08 xmudrii