go test ./... may break the current cluster set on kubeconfig

[wpjunior]

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

[heinrichgrt]

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.

[openshift-bot]

Issues go stale after 90d of inactivity.

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.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

[wpjunior]

This issue is important to cluster safety

[wpjunior]

/reopen

[openshift-ci]

@wpjunior: Reopened this issue.

Details

In response to this:

/reopen

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.

[heinrichgrt]

I do agree with @wpjunior this is a serious and very dangerous behaviour in the operator-sdk. I am a little bit annoyed that there is no response at all from the developer team.