[BETA API] With the v1beta1 changes introduced, need to determine the scope for test changes required

[apoorvajagtap]

Is there an existing issue for this?

• I have searched the existing issues

Anything else?

As #1352 introduces changes to samples of all the CRs, which might affect the existing e2e test cases. Raising this issue to discuss the scope of test cases that need immediate attention.

[apoorvajagtap]

@qu1queee @SaschaSchwarze0 I can observe that we have few YAML examples in test/data, which are being used within the test suites. Should these be updated as per v1beta1?

[SaschaSchwarze0]

@qu1queee @SaschaSchwarze0 I can observe that we have few YAML examples in test/data, which are being used within the test suites. Should these be updated as per v1beta1?

It would make sense to not migrate everything to Beta in test/data but to retain some Alpha objects to keep them covered (especially relevant when alpha eventually is not anymore the stored version).

[qu1queee]

From refinement, @apoorvajagtap to introduce some changes related to duplicate e2e tests. We will sync on this topic after that. Per the discussion, we do not have clarity on the best approach for e2e tests. The options are:

• move e2e to v1beta1, consequence is that we lose testing for alpha once the storage version becomes beta(v0.13.0 release)
• introduce e2e tests for both versions.