Is your feature request related to a problem? Please describe.
The controller can watch external targets out of the box. The chart makes assumptions which do not hold in certain scenarios (watching external cluster). A new values block should allow for several related values to be configured accordingly.
Describe the solution you'd like
Specifically (watch values block):
- Leader election enable/disable
- Leader election namespace
- kubeconfig secret (for the target cluster)
In addition to that, when e.g. watch.targetClusterKubeconfig secret is set: skip creation of controller (host) cluster role and role binding.
The chart should ideally support (template output) with the setup of the target / watch cluster. Alternatively a kustomization can work too.
Describe alternatives you've considered
None, requires patched deployment currently.
Additional context
Needs --skip-crds added to docs.
Is your feature request related to a problem? Please describe.
The controller can watch external targets out of the box. The chart makes assumptions which do not hold in certain scenarios (watching external cluster). A new values block should allow for several related values to be configured accordingly.
Describe the solution you'd like
Specifically (
watchvalues block):In addition to that, when e.g. watch.targetClusterKubeconfig secret is set: skip creation of controller (host) cluster role and role binding.
The chart should ideally support (template output) with the setup of the target / watch cluster. Alternatively a kustomization can work too.
Describe alternatives you've considered
None, requires patched deployment currently.
Additional context
Needs
--skip-crdsadded to docs.