Chip Zoller
Chip Zoller
There's no logging for only errors. If level 1 is still too high, you can set to 0 to disable the logging.
Probably not a good issue for a beginner.
This could potentially be solved by https://github.com/kyverno/kuttl/issues/22.
The expectation is that we use a tool like kuttl to run automated tests using the `kyverno apply` command just like we do with kuttl e2e tests or `kyverno test`...
No, you don't need to add any code, you just need to write kuttl (e2e) tests that use `kyverno apply`. See [here](https://github.com/kyverno/kyverno/blob/main/test/conformance/kuttl/README.md).
For those assigned and not currently working on this, kindly unassign yourself so others may pick it up.
We now use [Chainsaw](https://github.com/kyverno/kyverno/tree/main/test/conformance/chainsaw) for conformance tests which has its own [site](https://kyverno.github.io/chainsaw/latest/).
The objective is to use Chainsaw to write tests for the `kyverno apply` command to ensure it works as expected both against and outside of a Kubernetes cluster. I recommend...
Tests should only be written in Chainsaw. If you look in the parent directory as well as the policy library (kyverno/policies) you can see hundreds of examples of Chainsaw tests.
You need to be familiar with the Kyverno CLI's `apply` command to work on this issue. Please read [the docs](https://kyverno.io/docs/kyverno-cli/#apply) if you are not familiar and spend some time using...