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

Migrate Infra code to separate repo called k/infrastructure #6609

Open
upodroid opened this issue Mar 21, 2024 · 5 comments
Open

Migrate Infra code to separate repo called k/infrastructure #6609

upodroid opened this issue Mar 21, 2024 · 5 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.

Comments

@upodroid
Copy link
Member

The code in the infra folder should be moved to a new repository called kubernetes/infrastructure

You can have a look at https://github.com/borg-land/k8s.io/tree/new-infra-repo for what I think the repo will look like. We want to store only terraform code for our infrastructure and Kubernetes manifests in that repo.

I'm going to use that repo for terraform automation and unify all the kubernetes manifests for all our clusters to a central location.

/cc @xmudrii @ameukam @BenTheElder @dims

@upodroid upodroid added the sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. label Mar 21, 2024
@xmudrii
Copy link
Member

xmudrii commented Mar 25, 2024

I'm +1 for this change, we also had a chance to discuss it at KubeCon and I think it would help to implement better CI/CD workflows with Prow and Argo. However, I'd like to experiment a bit more with the repo structure, I'll try to do it in the next day or two and get back with results.

@BenTheElder
Copy link
Member

I'm kind of -1 on this change, we have a lot of overlap between terraform and non-terraform (e.g. the bash, the IAM auditing, etc), I'd like to see the terraform automation we adopt be safer instead.

Also, anytime we move code to a new repo there's a lot of broken inbound links and general churn, so in most cases we've broken things out to make them easier to consume (e.g. using kind or prow the project without other random test-infra hackery), whereas this whole repo is soley infra configs for kubernetes.

@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 Jul 17, 2024
@xmudrii
Copy link
Member

xmudrii commented Jul 23, 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 Jul 23, 2024
@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 Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. 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