Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
2 tasks
Tracked by #5169
xmudrii opened this issue Apr 25, 2023 · 7 comments
Open
2 tasks
Tracked by #5169
Labels
area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure area/infra Infrastructure management, infrastructure design, code in infra/ help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Milestone

Comments

@xmudrii
Copy link
Member

xmudrii commented Apr 25, 2023

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

/priority important-longterm

@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 25, 2023
@xmudrii
Copy link
Member Author

xmudrii commented Apr 25, 2023

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

@k8s-ci-robot k8s-ci-robot added this to the v1.28 milestone Apr 25, 2023
@k8s-ci-robot k8s-ci-robot added sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. area/infra Infrastructure management, infrastructure design, code in infra/ area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Apr 25, 2023
@sbdtu5498
Copy link

@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
Copy link
Contributor

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
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2024
@xmudrii
Copy link
Member Author

xmudrii commented Jan 22, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 22, 2024
@xmudrii
Copy link
Member Author

xmudrii commented Feb 12, 2024

/unassign @pkprzekwas
/help
/milestone v1.31

@k8s-ci-robot
Copy link
Contributor

@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:

/unassign @pkprzekwas
/help
/milestone v1.31

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.28, v1.31 Feb 12, 2024
@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure area/infra Infrastructure management, infrastructure design, code in infra/ help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Projects
None yet
Development

No branches or pull requests

5 participants