Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
terraform-k8s & Kubernetes Version
terraform-k8s: 1.1.0
Kubernetes: 1.21
Expected Behavior
We want to deploy operator instances in a different namespace to the one they manage. This is so that developers who have control over that namespace are able to deploy Workspace CRDs into it but are unable to see/manage the Terraform operator instance.
The leader election ID should be set dynamically and should be unique per instance of the helm chart.
Deploy 2 instances of the operator into the same namespace that both monitor 2 different namespaces. Only one will be monitoring its namespace (the one that won the election).
Community Note
terraform-k8s & Kubernetes Version
terraform-k8s: 1.1.0 Kubernetes: 1.21
Expected Behavior
We want to deploy operator instances in a different namespace to the one they manage. This is so that developers who have control over that namespace are able to deploy Workspace CRDs into it but are unable to see/manage the Terraform operator instance.
The leader election ID should be set dynamically and should be unique per instance of the helm chart.
Actual Behavior
The leader election ID is hard-coded so all instances of the operator will share the same ID.
Steps to Reproduce
Deploy 2 instances of the operator into the same namespace that both monitor 2 different namespaces. Only one will be monitoring its namespace (the one that won the election).