feat(gw-operator): Deprecate kube-rbac-proxy

[levaitamas]

fixes #47

[rg0now]

Should we also remove the rbac-proxy from the Prometheus chart? See stunner-prometheus/templates/kube-state-metrics.yaml, helm/stunner-prometheus/templates/node-exporter.yaml and helm/stunner-prometheus/values.yaml.

[levaitamas]

Should we also remove the rbac-proxy from the Prometheus chart? See stunner-prometheus/templates/kube-state-metrics.yaml, helm/stunner-prometheus/templates/node-exporter.yaml and helm/stunner-prometheus/values.yaml.

That's a valid point. Does anyone use that chart? I mean, when I wanted to monitor STUNner for the https://www.webrtc-observer.org demo site, I had to do a lot of work to make that chart work as a proper monitoring solution (e.g., I had to attach storage, draw my dashboard, update config params here and there, etc.). That's why I see minimal value in maintaining the stunner-prometheus chart. I also propose to obsolete/remove it during the great refactor (#35).

[rg0now]

To what extent the stunner-prom helm chart can be integrated into the default helm chart? I mean, the prom operator customizations, adding the PodMonitors, setting the metric endpoint in STUNner's default Dataplane, these can all be added to the main install chart as optional features, no? Wdyt?

But I agree, if no user shows up let's just remove the prom chart

[levaitamas]

cc @davidkornel

[davidkornel]

LGTM however we have received an pr regarding the rbac-proxy resources #50