Kubewarden is an open source security project, hosted by the CNCF. As a vendor neutral project, we welcome a broad range of contributions.
This repository aims to document the evolution process of The Kubewarden Project.
It provides a space for the community to work together, discuss ideas, and document processes. It is also a place to make decisions that regard the whole Kubewarden organization and define rules and structures that span beyond the extent of a single repository.
Table of Contents
We recommend you read our Quickstart page at docs.kubewarden.io to get familiarized with Kubewarden and what it aims to achieve. From then, feel free explore the full documentation to understand all its features.
We follow the CNCF Code of Conduct.
To report an issue, please contact cncf-kubewarden-maintainers@lists.cncf.io or any of the individual members of the CNCF Code of Conduct Committee to submit your report. For more detailed instructions on how to submit a report, including how to submit a report anonymously, please see our Incident Resolution Procedures. You can expect a response within three business days.
You can find the list of current maintainers in the MAINTAINERS.md file.
Information about our roadmap process is available in the ROADMAP.md file.
Get in contact with us:
- Slack: #kubewarden and #kubewarden-dev.
- GitHub discussions in this repository.
- Maintainers mailing list:
cncf-kubewarden-maintainers, followed by@, followed bylists.cncf.io
We host regular online meetings for contributors, adopters, maintainers, and anyone else interested. These meetings usually take place on the second Thursday of the month at 4 PM UTC.
We're a friendly group, so please feel free to join us!
See the contributing guide and the code of conduct.
See the security policy for more information about how to report any security issues.
The Kubewarden Project applies a straightforward adoption model for its repositories. Each repository is given a scope, which outlines its purpose, and a status that indicates its maturity level.
For more detailed information, please refer to the REPOSITORIES.md file.
In the sections that follow, we present the repositories, grouped by their scope.
Furthermore, some of the roles of the components listed below are described in the components.md file.
Core repositories, are critically important as they are essential for building, installing, running and using Kubewarden.
| NAME | STATUS | DESCRIPTION |
|---|---|---|
| kubewarden/kubewarden-controller |  |
Manage admission policies in your Kubernetes cluster with ease |
| kubewarden/policy-server | |
Webhook server that evaluates WebAssembly policies to validate Kubernetes requests |
| kubewarden/audit-scanner | |
Reports evaluation of existing Kubernetes resources with your already deployed Kubewarden policies |
| kubewarden/kwctl | |
Go-to CLI tool for Kubewarden users |
| kubewarden/helm-charts | |
Helm charts for the Kubewarden project |
| kubewarden/policy-evaluator | |
Rust library used by Kubewarden to evaluate policies with a given input, request to evaluate and settings. |
| kubewarden/policy-fetcher | |
Rust library used by Kubewarden to pull policies from OCI registries and HTTP servers. |
| NAME | STATUS | DESCRIPTION |
|---|---|---|
| kubewarden/automation | |
Automation scripts for the management of the Kubewarden organization on GitHub |
| kubewarden/load-testing | |
HTTP load to stress policy-server |
| kubewarden/rancher-kubectl-builder | |
Workflow to rebuild and sign rancher/kubectl image |
| kubewarden/github-actions | |
GitHub actions used by the Kubewarden project |
| kubewarden/kubewarden-end-to-end-tests | |
Files used to run Kubewarden end-to-end tests |
All the policies maintained by the Kubewarden team are stored in the kubewarden/policies and kubewarden/rego-policies-library repositories.
For policies across all of GitHub, see the
kubewarden-policy topic tag.
The following repositories are the template the policy authors can use to write their own policies. Checkout the Kubewarden documentation for more information about how to write policies.
| NAME | STATUS | DESCRIPTION |
|---|---|---|
| kubewarden/dotnet-policy-template |  |
A template repository to quickly scaffold a Kubewarden policy written with C# |
| kubewarden/gatekeeper-policy-template | |
A template repository to quickly port a Gatekeeper policy to Kubewarden |
| kubewarden/go-policy-template | |
A template repository to quickly scaffold a Kubewarden policy written with Go language |
| kubewarden/go-wasi-policy-template | |
Template of a plain WASI policy written using Go |
| kubewarden/opa-policy-template | |
A template repository to quickly port a Open Policy Agent policy to Kubewarden |
| kubewarden/rust-policy-template | |
A Kubewarden Rust policy template to be used with cargo-generate |
| kubewarden/swift-policy-template |  |
A template repository to quickly scaffold a Kubewarden policy written with Swift language |
| kubewarden/js-policy-template | |
A template repository to quickly scaffold a Kubewarden policy written with TypeScript/JavaScript |
For policy templates across all of GitHub, see the kubewarden-policy-template topic tag.
The following repositories are the SDKs the policy authors can use to write their own policies. Checkout the Kubewarden documentation
| NAME | STATUS | DESCRIPTION |
|---|---|---|
| kubewarden/policy-sdk-dotnet | |
Kubewarden Policy SDK for the .NET platform |
| kubewarden/policy-sdk-go | |
Kubewarden Policy SDK for the Go programming language |
| kubewarden/policy-sdk-rust | |
Kubewarden Policy SDK for the Rust programming language |
| kubewarden/policy-sdk-swift | |
Kubewarden Policy SDK for the Swift programming language |
| kubewarden/policy-sdk-js | |
Kubewarden Policy SDK for the JavaScript/TypeScript programming language |
For policy SDKs across all of GitHub, see the kubewarden-policy-sdk topic tag.
Finally, some repositories have a special meaning and do not fit the above scopes. They serve a particular purpose or function in the Kubewarden organization and are curated by maintainers.
See REPOSITORIES.md for more information.
| NAME | STATUS | DESCRIPTION |
|---|---|---|
| kubewarden/fleet-example | |
Example of Rancher Fleet bundle for Kubewarden |
| kubewarden/docs | |
Kubewarden's documentation |
| kubewarden/rfc | |
Kubewarden's RFCs |
| kubewarden/.github | |
Special GitHub repository |
| kubewarden/kubewarden.io | |
Kubewarden website |
| kubewarden/gostubpkg | |
gostubpkg is a tool for generating stubs of Go packages |
| kubewarden/k8s-objects-generator | |
CLI tool that generates Kubernetes Go types that can be used with TinyGo starting from the official OpenAPI spec |
| kubewarden/strfmt | |
A stripped down version of go-openapi/strfrm that works with TinyGo |
| kubewarden/k8s-objects | |
Kubernetes Go types that can be used with TinyGo |
| kubewarden/utils | |
Utils scripts used by the Kubewarden team and users. |
| kubewarden/gtmpl-rust | |
golang text/template for rust |
| kubewarden/policy-charts | |
Poliy Helm charts for Rancher UI |
In general, a repository can be archived at the discretion of Kubewarden community. Usually, maintainers can decide to archive a project that has not been maintained for a long time or does not fit the guidelines for the projects under the Kubewarden GitHub's organization anymore. In other cases, a repository is archived to reserve its name for future use.
The list of archived repositories can be found here.
