Bug Report
What did you do?
I posted about this issue in slack. I've upgraded from 0.10.0 to 0.14.0. The operator is releasing into the same namespace that it is deployed in instead of where the CR's are created. This was confirmed by @joelanford on slack.
What did you expect to see?
The resources created by the operator are created in the CR's namespace.
What did you see instead? Under which circumstances?
The resources created by the operator are created in the operator's namespace.
Environment
- Kubernetes version information:
Possible Solution
Additional context
Add any other context about the problem here.
Bug Report
What did you do?
I posted about this issue in slack. I've upgraded from 0.10.0 to 0.14.0. The operator is releasing into the same namespace that it is deployed in instead of where the CR's are created. This was confirmed by @joelanford on slack.
What did you expect to see?
The resources created by the operator are created in the CR's namespace.
What did you see instead? Under which circumstances?
The resources created by the operator are created in the operator's namespace.
Environment
operator-sdk version:
0.14.0
go version:
Kubernetes cluster kind:
Are you writing your operator in ansible, helm, or go?
Helm
Possible Solution
Additional context
Add any other context about the problem here.