breaking change in 3.19.x for restricted cluster access

[mozemke]

hi!

the changes made in #379 seem to have been breaking an existing use case.
to be precise:

with 3.18.x we were able to run the exporter in a multi tenant environment. By setting --include-namespace=ns1 --include-namespace=ns2 .. we were able to avoid needing cluster wide rights.
With the changes mentioned above you change the functionality of listNamespacesToWatch now even though no labels are set it needs cluster wide permissions.

Proposal:
a) check if include labels are set before making a cluster wide search
b) only search for include-labels OR include-namespaces, instead of offering both at the same time

Looking forward! :)

[piotrk167]

@enix When can we expect a fix for that issue?

[plaffitt]

Sorry for the inconvenience, I just made a PR to fix the issue, hoping to merge it soon. I went for the solution a) as the solution b) would theoretically introduce another breaking change (when using include-namespace-labels + exclude-namespaces).