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

kubernetes / k8s.io

Code and configuration to manage Kubernetes project infrastructure, including various *.k8s.io sites

https://git.k8s.io/community/sig-k8s-infra

Apache License 2.0

739 stars 825 forks source link

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

Open xmudrii opened 9 months ago

xmudrii commented 9 months ago

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

k8s-triage-robot commented 6 months ago

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

xmudrii commented 6 months ago

/remove-lifecycle stale

k8s-triage-robot commented 3 months ago

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

xmudrii commented 3 months ago

/remove-lifecycle stale

xmudrii commented 3 months ago

/unassign

k8s-triage-robot commented 4 days ago

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

xmudrii commented 2 days ago

/remove-lifecycle stale