You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the project bootstrap using operator-sdk, the directory test/e2e is created, if you run a go test ./... you may lose cert-manager and prometheus-operator on the current cluster set on kubeconfig.
What did you expect to see?
I think that is a accident, but we might prevent similar situations from happening to others. go test ./... should not trigger the e2e tests, we should use a environment variable to trigger e2e tests just on Makefile
The text was updated successfully, but these errors were encountered:
wpjunior
changed the title
go test ./... may broke the current cluster set on kubeconfig
go test ./... may break the current cluster set on kubeconfig
Aug 5, 2024
The same happend to us today. We deleted cert-manager and prometheus on two clusters. This is really dangerous. It would be great, if you would set the k8s-context in the Makefile or in the test itself to something like operator-kind and not simply using users current k8s-context.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
Bug Report
What did you do?
After the project bootstrap using operator-sdk, the directory test/e2e is created, if you run a go test ./... you may lose cert-manager and prometheus-operator on the current cluster set on kubeconfig.
What did you expect to see?
I think that is a accident, but we might prevent similar situations from happening to others. go test ./... should not trigger the e2e tests, we should use a environment variable to trigger e2e tests just on Makefile
The text was updated successfully, but these errors were encountered: