This repository contains tools and configuration files for the testing and automation needs of the Kubernetes project.
Our architecture diagram provides an (updated #13063) overview of how the different tools and services interact.
Kubernetes uses a prow instance at prow.k8s.io to handle CI and
automation for the entire project. Everyone can participate in a
self-service PR-based workflow, where changes are automatically deployed
after they have been reviewed. All job configs are located in config/jobs
- Add or update job configs
- Delete job configs
- Test job configs locally
- Trigger jobs on PRs using bot commands
- Testgrid shows historical test results over time (testgrid)
- Triage shows clusters of similar test failures across all jobs (triage)
- Deck shows what jobs are running or have recently run in prow (prow/cmd/deck)
- PR Status shows what needs to be done to get PRs matching a GitHub Query to merge (prow/cmd/tide)
- Tide History shows what actions tide has taken over time to trigger tests and merge PRs (prow/cmd/tide)
- Tide Status shows what PRs are in tide pools to be tested and merged (prow/cmd/tide)
- boskosmanages pools of resources; our CI leases GCP projects from these pools
- experimentis a catchall directory for one-shot tools or scripts
- gcswebis a UI we use to display test artifacts stored in public GCS buckets
- ghproxyis a GitHub-aware reverse proxy cache to help keep our GitHub API token usage within rate limits
- gopherageis a tool for manipulating Go coverage files
- label_synccreates, updates and migrates GitHub labels across orgs and repos based on- labels.yamlfile
- kettleextracts test results from GCS and puts them into bigquery
- kubetest2is how our CI creates and e2e tests kubernetes clusters
- metricsruns queries against bigquery to generate metrics based on test results
- robots/commenteris used by some of our jobs to comment on GitHub issues
Please see CONTRIBUTING.MD