Kubernetes project infrastructure, managed by the kubernetes comunity via wg-k8s-infra
apps: community-managed apps that run on the community-managedaaaclustergcsweb: instance of gcsweb at https://gcsweb.k8s.io - owned by sig-testingkubernetes-external-secrets: instance of kubernetes-external-secrets - owned by sig-testingperfdash: instance of perfdash - owned by sig-scalabilityprow: work-in-pogress instance of prow - owned by sig-testingpublishing-bot: instance of publishing-bot - owned by sig-releasesippy: 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-experiencetriageparty-release: instance of triage-party - owned by sig-release
audit: scripts to export all relevant gcp resources, and the most recently-reviewed exportcert-manager: instance of cert-manager for theaaacluster - owned by ???dns: DNS for kubernetes.io and k8s.iogroups: google groups on the kubernetes.io domainhack: scripts used for development, testing, etc.images: container images published togcr.io/k8s-staging-infra-toolsinfra/gcp: scripts and data to manage our GCP infrastructureclusters/modules: terraform modules intended for re-use within this repoclusters/projects: terraform to manage (parts of) GCP projects
k8s.gcr.io: container images published by the project, promoted fromgcr.io/k8s-staging-*reposk8s.io: instance of nginx that provides redirects/reverse-proxying for k8s.io and its subdomains - owned by sig-contributor-experience and sig-testing (TODO(kubernetes#2150) migrate to apps/)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?
artifactsartifactserverpolicies
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
