At least with out-of-the-box configurations, it seems keycloak operator only tracks its own namespace.
In projman, I set the clients to be deployed in the Keycloak operator namespace: https://github.com/CloudVE/projman-helm/blob/master/projman/values.yaml#L47 but it's still settable. It'd be ideal to have it a config option here as well, but not entirely sure what the most elegant way to do it is off the top of my head. Hardcoding it is also probably fine for our realistic usecases
Coverage increased (+0.05%) to 93.549% when pulling d8cb554d928e3bd1174f6dd4958083d3b2ea4251 on kc-operator-namespace into 1cda3c4863f522a50bdc514fa12919e66c54234c on master.
At least with out-of-the-box configurations, it seems keycloak operator only tracks its own namespace. In projman, I set the clients to be deployed in the Keycloak operator namespace: https://github.com/CloudVE/projman-helm/blob/master/projman/values.yaml#L47 but it's still settable. It'd be ideal to have it a config option here as well, but not entirely sure what the most elegant way to do it is off the top of my head. Hardcoding it is also probably fine for our realistic usecases