CI/CD
CNCF covers CI needs for hosted projects. Projects choose their own CI platform; CNCF staff recommend GitHub Actions where possible.
Available options
| Option | What you get | How to get it |
|---|---|---|
| GitHub Actions on CNCF's GitHub Enterprise | Larger runners, and runners hosted across environments using Actions Runner Controller | CNCF Service Desk |
| Prow GitHub Actions | Prow-style chat-ops (/lgtm, /approve, /retest, /ok-to-test), reviewers from OWNERS files, automatic merging, and label sync, running as a GitHub Actions workflow. Maintained by CNCF staff. | Add the workflow to your repository. See Get started. |
| Prow | The Kubernetes-based CI system used by Kubernetes | CNCF Service Desk |
| Other CI platforms | Projects may use the platform that fits their needs | CNCF Service Desk |
Prow GitHub Actions
@cncf/prow-github-actions brings Prow's chat-ops and project management to a GitHub Actions workflow, with no cluster to run.
- Copy
templates/workflow-templates/prow.ymlto.github/workflows/prow.yml. If your policy forbidspull_request_target, useprow-pull-request.ymlinstead. - Run the
label-syncjob once from Actions → Prow → Run workflow so the labels exist. - Optional: add a
prow.yamlto the repository, or to your organization's.githubrepository, for label families andneeds-*rules.
tip
Setting up a whole organization? Start with Prow for your organization.
See the installing guide, command reference, and configuration for details.