k8s.io

Kubernetes project infrastructure, managed by the kubernetes comunity via wg-k8s-infra

• apps: community-managed apps that run on the community-managed aaa cluster
  • gcsweb: instance of gcsweb at https://gcsweb.k8s.io - owned by sig-testing
  • k8s.io: instance of nginx that provides redirects/reverse-proxying for k8s.io and its subdomains - owned by sig-contributor-experience and sig-testing
  • kubernetes-external-secrets: instance of kubernetes-external-secrets - owned by sig-testing
  • perfdash: instance of perfdash - owned by sig-scalability
  • prow: work-in-pogress instance of prow - owned by sig-testing
  • publishing-bot: instance of publishing-bot - owned by sig-release
  • sippy: instance of sippy at https://sippy.k8s.io - owned by sig-architecture (on behalf of wg-reliability)
  • slack-infra: instance of slack-infra including https://slack.k8s.io - owned by sig-contributor-experience
  • triageparty-release: instance of triage-party - owned by sig-release
• audit: scripts to export all relevant gcp resources, and the most recently-reviewed export
• dns: DNS for kubernetes.io and k8s.io
• groups: google groups on the kubernetes.io domain
• hack: scripts used for development, testing, etc.
• images: container images published to gcr.io/k8s-staging-infra-tools
• infra/gcp: scripts and data to manage our GCP infrastructure
  • bash/namespaces: scripts and data to manage K8s namespaces and RBAC for aaa
  • bash/prow: scripts and data used to manage projects used for e2e testing and managed by boskos
  • bash/roles: scripts and data to manage custom GCP IAM roles
  • terraform/modules: terraform modules intended for re-use within this repo
  • terraform/projects: terraform to manage (parts of) GCP projects
• k8s.gcr.io: container images published by the project, promoted from gcr.io/k8s-staging-* repos
• policy: open policy agent policies used by conftest to validate resources in this repo
• registry.k8s.io: work-in-progress to support cross-cloud mirroring/hosting of containers and binaries

TODO: are these actively in use or should they be retired?

• artifacts
• artifactserver

We provide a publicly viewable billing-report accessible to members of [[email protected]]

Please see https://git.k8s.io/community/wg-k8s-infra for more information