Cass-operator tests and makefile targets reference default kubecontext

[Miles-Garnsey]

What happened?

In certain makefile targets and test helpers the cass-operator tests try to use the default kubecontext to create or query resources.

Did you expect to see something different?

Yes. The default context should never be used because - if a developer is working on customer or production clusters while also working on cass-operator - there is a risk that the tests will cause damage to the production/customer cluster.

A kubeconfig containing only kind clusters should be created in a ./build directory and the kind contexts should be used as the default kubeconfig.

How to reproduce

$ mv ~/.kube/config ~/
$ make integ-test
kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.5.3/cert-manager.yaml
The connection to the server localhost:8080 was refused - did you specify the right host or port?
make: *** [cert-manager] Error 1
mv  ~/config ~/.kube/

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-49