Closed bentito closed 2 years ago
Still not the proper spot 😅 but let's keep it here. The issue, I think, is due to the fact that recent Fabric8 client version seem to be losing the current context. If you use a tool such as kubens
or oc project
to make sure you have an active/selected namespace/project before running your operator, the issue should go away. More recent versions of the SDK actually tells you about it when this occurs.
Ah indeed, oc project default
failed to work easily for a Kind cluster, but tried:
kubectl config set-context --current --namespace=default
and it worked, so that's an easy workaround. Thanks!
Yes, this didn't use to be such an issue before, though… Not sure why it's the case now.
Bug Report
What did you do?
Maven quarkus dev mode fails when trying to test operator on Kind cluster.
What did you expect to see?
mvn quarkus:dev
should work.What did you see instead? Under which circumstances?
On a Kind cluster,
mvn quarkus:dev
fails as follows:Same code works when used with dev mode with another type of cluster, for instance, CRC, minikube, etc.
Environment
Kubernetes cluster type:
Kind 0.12.0 (on MacOS with Homebrew,
brew install kind
)$ Mention java-operator-sdk version from pom.xml file