Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Conformance tests for Kyverno upgrade #10155

Open
2 tasks done
realshuting opened this issue May 1, 2024 · 0 comments
Open
2 tasks done

[Feature] Conformance tests for Kyverno upgrade #10155

realshuting opened this issue May 1, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request release-critical Critical issues which MUST be addressed in the specified milestone. These cannot get bumped. test Tasks related to unit/e2e tests.

Comments

@realshuting
Copy link
Member

Problem Statement

Currently there's no automated test for the Kyverno upgrade. This is critical for Kyverno's stability upon new releases.

All existing conformance tests target a single policy and check its expected result. While in 1.12.0 release we found an issue when applying policies concurrently and Kyverno returned inconsistent results. One of the common use cases to test out is Kyverno PSS policies. Covering Kyverno upgrade by conformance tests, specifically for PSS policies, is a good starting point.

Solution Description

This test was added to verify Kyverno PSS policies, the same test can be extended for the Kyverno upgrade.

https://github.com/kyverno/kyverno/tree/main/test/conformance/chainsaw/validate/clusterpolicy/standard/psa/concurrent-policy-execution

Alternatives

No response

Additional Context

No response

Slack discussion

No response

Research

  • I have read and followed the documentation AND the troubleshooting guide.
  • I have searched other issues in this repository and mine is not recorded.
@realshuting realshuting added enhancement New feature or request test Tasks related to unit/e2e tests. labels May 1, 2024
@realshuting realshuting added this to the Kyverno Release 1.13.0 milestone May 1, 2024
@realshuting realshuting added the release-critical Critical issues which MUST be addressed in the specified milestone. These cannot get bumped. label May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request release-critical Critical issues which MUST be addressed in the specified milestone. These cannot get bumped. test Tasks related to unit/e2e tests.
Projects
None yet
Development

No branches or pull requests

2 participants