eks-prow-build-cluster: Deploy GitOps solution for Terraform and Kubernetes resources

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

735 stars 822 forks source link

eks-prow-build-cluster: Deploy GitOps solution for Terraform and Kubernetes resources #5170

Open xmudrii opened 1 year ago

xmudrii commented 1 year ago

This is a placeholder/tracking issue for deploying some GitOps solution to deploy Terraform and Kubernetes resources for eks-prow-build-cluster. We're yet to discuss and decide upon how we want to handle this.

### Tasks
- [ ] Research what GitOps solution we should use
- [ ] Write a proposal describing how should we implement the given GitOps solution

/priority important-longterm

xmudrii commented 1 year ago

/milestone v1.28 /sig k8s-infra /area infra /area infra/aws /kind cleanup

sbdtu5498 commented 1 year ago

@xmudrii I have past experience working with Argo CD. I can create a design doc for the purpose taking into consideration Argo CD, Flux CD, and Flamingo ( aka the Flux subsystem for Argo).

pkprzekwas commented 1 year ago

Hi @sbdtu5498 , I was planing to start working on this issue today. Likewise, I'm also experienced mainly with ArgoCD. If you want to do help and prepare a summary of pros and cons for each solution that would be welcomed.

I guess we don't expect to have any complex deployment workflows. Our main goal is to keep maintenance as simple as possible. Thus, any of tools you've listed should work just fine.

I'm not sure if we're going to get service account with write permissions to commit directly to k8s.io repo, so we might now be able to setup flux with image refresh functionality.

/assign pkprzekwas

k8s-triage-robot commented 10 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 9 months ago

/remove-lifecycle stale

xmudrii commented 9 months ago

/unassign @pkprzekwas /help /milestone v1.31

k8s-ci-robot commented 9 months ago

@xmudrii: This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

Why are we solving this issue?
To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
Does this issue have zero to low barrier of entry?
How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to [this](https://github.com/kubernetes/k8s.io/issues/5170): >/unassign @pkprzekwas >/help >/milestone v1.31 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.