Skip to content

E2E tests for different feature gate states #447

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

Open
m1kola opened this issue Oct 9, 2023 · 1 comment
Open

E2E tests for different feature gate states #447

m1kola opened this issue Oct 9, 2023 · 1 comment

Comments

@m1kola
Copy link
Member

m1kola commented Oct 9, 2023

Now that we have this feature gate:

ForceSemverUpgradeConstraints: {Default: false, PreRelease: featuregate.Alpha},

We should find a way to run E2E in CI with different states of feature gates.


One option is to use kustomze overlays for different configurations (potentially using components). However this means that we need one overlay for every permutation which might become a bit messy.

We can also look into Kubernetes tests and see what is done there and whether we can re-use any tools/code (we use k8s.io/component-base/featuregate package for feature gates, same as Kubernetes).

@m1kola
Copy link
Member Author

m1kola commented Oct 12, 2023

It was suggested in #444 (comment) as an option to E2E default state and cover other states with fast tests (unit/integration tests).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant