shuting
shuting
HI @lhajouji - thanks for the suggestions, and PRs are welcome😃 We could start by adding a table of content for quick navigation and filling out details as follows.
A bunch of tests failed, converting to draft as we need test coverage as well. @Mohdcode - can you work on those changes?
> need help Please elaborate.
> I would appreciate any insights or suggestions on how to resolve these test failures , i can't understand all Which ones are you trying to fix?
> milestone label , chainsaw test and conformance test/conformance-required (pull_request) Those Chainsaw tests seem to be flaky, re-triggered the test.
@Mohdcode - the existing tests seem fine after re-running. We are missing test coverage for your change, and you add?
> I wrote a test file or is there something else I should understand. I missed it, was looking for Chainsaw tests.
An option is to extract pod's spec from all controllers as a variables, and validate againt it, see slide 22 from this [presentation](https://static.sched.com/hosted_files/kccnceu2025/03/evaporating_kubernetes_security_risk.pdf).
Is this [expected](https://github.com/kyverno/kyverno/actions/runs/16256933205/job/45894782430?pr=13476)? ``` Error: failed to run test (error: failed to load resources (field "labels" is null)) ```
> Hi @realshuting, > > Regarding your [comment](https://github.com/kyverno/kyverno/pull/13476#issuecomment-3159700375) — since this PR introduces the ability to disallow or drop empty fields in resource manifests using the `--drop-empty-fields` flag, it leads...