Fetching the latest programs, projects, and workspace data.

Support a new type of Kyverno rule to delete resources based on various criterias, such as the type, age, metadata and status. Upstream Issue (URL): - https://github.com/kyverno/kyverno/issues/3483 - https://github.com/kyverno/KDP/pull/25
Showing 5 of 50 projects. Click any project card for scope, mentors, and proposal studio.
Currently Kyverno uses Chainsaw as the primary testing tool, which executes end-to-end tests on a real cluster. While this provides a large test coverage, it takes a long time to be executed and is also used to test very basic/simple cases. This project is about creating a framework to allow and simplify the creation of integration tests on the code level, without spinning up an actual cluster. This allows easier and faster testing locally as well as in our CI pipelines.
Build an Envoy plugin to support authorisation based on Kyverno policies. Expected Outcome: Enable users to perform autorisation with similar concepts as kyverno and kyverno-JSON using policies.
The Kyverno CLI does not have a formalized schema with proper validation for its test command. Create a formal schema which is documented allowing for full validation and related other capabilities which enhance its usage. Upstream Issue (URL): * https://github.com/kyverno/kyverno/issues/2323 * https://github.com/kyverno/kyverno/issues/2315 * https://github.com/kyverno/kyverno/issues/2302 * https://github.com/kyverno/kyverno/issues/2857 * https://github.com/kyverno/kyverno/issues/2945 * https://github.com/kyverno/kyverno/issues/3271
Support the mutateExisting rule in Kyverno CLI Expected Outcome: - Allow users to be able to apply mutate existing policies to resources from 1. file systems; 2. clusters.
Implement a new policy rules autogen system based on extracting the pod spec from higher-level controllers. Expected Outcome: 1. The new system works by applying the same rules on the extracted pod spec instead of generating new rules for higher-level controllers 2. The system treats pods and higher-level controllers exactly the same from a policy stand point