-
Notifications
You must be signed in to change notification settings - Fork 41.5k
DRA: CRUD conformance tests #133747
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
DRA: CRUD conformance tests #133747
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test pull-kubernetes-audit-kind-conformance DeleteCollection not implemented yet, checking whether the job finds that... |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Promoting real tests (#133132) turned out to be harder than expected (should be rewritten to be self-contained, additional reviews, etc.).
They would not achieve 100% endpoint+operation coverage because real tests only use some of the operations. Therefore each API type has to be covered with CRUD-style tests which only exercise the apiserver, then maybe additional functional tests can be added later (depending on time and motivation).
Which issue(s) this PR is related to:
#114183
#133691
KEP: kubernetes/enhancements#4381
Special notes for your reviewer:
The machinery for testing different API types is meant to be reusable, so it gets added in the new e2e/framework/conformance helper package.
Does this PR introduce a user-facing change?