kwctl is the go-to CLI tool for Kubewarden users.
Think of it as the docker CLI tool if you were working with containers.
As a policy author
- e2e testing of your policy. Test your policy against crafted Kubernetes
requests, and ensure your policy behaves as you expect. You can even test
context-aware policies, that require access to a running cluster.
- Embed metadata in your Wasm module, so the binary is annotated with the
permissions it needs to execute.
- Publish policies to OCI registries.
- Generate initial ClusterAdmissionPolicy scaffolding for your policy.
As a cluster administrator
- Inspect remote policies. Given a policy in an OCI registry, or in an HTTP
server, show all static information about the policy.
- Dry-run of a policy in your cluster. Test the policy against crafted
Kubernetes requests, and ensure the policy behaves as you expect given the
input data you provide. You can even test context-aware policies, that
require access to a running cluster, also in a dry-run mode.
- Generate ClusterAdmissionPolicy scaffolding for a given policy.
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
Each row is recorded package-index metadata for one version, architecture, suite, and repository. Names, URLs, and sizes are source-reported; a link is a potentially mutable retrieval location, not an OpenFactory redistribution claim or proof that OpenFactory retained the artifact bytes.
