Possibility to deploy the operator in an arbitrary namespace

[guicassolato]

Authorino Operator's deployment manifests, generated using this make target, currently enforce authorino-operator as the Kubernetes namespace to run the operator workload.

While on one hand that single-file manifest is very useful to install and deploy the Operator and the CRDs, changing the operator namespace, on the other hand, is not straightforward, requiring all occurrences of namespace: authorino-operator in the file, as well as the name of Namespace resource itself, to be properly replaced.

Except in the RoleBinding and ClusterRoleBinding resources, mentioning the Kubernetes namespace could be avoided, but in general, perhaps using a placeholder to ensure assertive replacement (e.g. making possible to rely on envsubst)? Another option would be relying more on Operator Lifecyle Manager to install the operator? Although it's not available by default in Kubernetes, but only in OpenShift.

[jjaferson]

@guicassolato The only problem with the OLM is that it doesn't come by default in Kubernetes which would generate a dependency on the operator, I would be more inclined to use envsubst to replace the operator namespace to use a custom one.