Skip to content

Clean up the tests and document test policy #2921

@camilamacedo86

Description

@camilamacedo86

What do you want to happen?

As discussed and agreed in the KubeBuilder meeting on Sep 08 2022: (Meeting: https://youtu.be/GzVcNr_F1SY we just need to support the latest 3 k8s releases and has no reason for we run the tests against so many versions as we do now see:

Screenshot 2022-09-10 at 19 45 33

In this way, we need to:

Following the details
a) Remove all tests done with v1beta1:

(We also need to remove the option to pass version v1beta1)

b) Remove the conditions that will get obsolete

c) All tests now are done with restricted mode true then we can remove the test: https://github.com/kubernetes-sigs/kubebuilder/blob/master/test/e2e/v3/plugin_cluster_test.go#L172

d) The same changes need to be applied under tests/e2e/v4/, see: https://github.com/kubernetes-sigs/kubebuilder/tree/master/test/e2e/v4

e) we can also remove the skip conditions from : https://github.com/kubernetes-sigs/kubebuilder/blob/master/test/e2e/deployimage/plugin_cluster_test.go

Extra Labels

/kind cleanup

Metadata

Metadata

Assignees

Labels

good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.kind/featureCategorizes issue or PR as related to a new feature.testingtriage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions