Controller Manager reports a kube-rbac-proxy warning

[sarroutbi]

Background

The Tang Operator Controller Manager reports a warning:

oc logs pod/tang-operator-controller-manager-7c8b6bf748-gsnq4 -n nbde

W0229 18:07:54.932304       1 kube-rbac-proxy.go:155] 
==== Deprecation Warning ======================

Insecure listen address will be removed.
Using --insecure-listen-address won't be possible!

The ability to run kube-rbac-proxy without TLS certificates will be removed.
Not using --tls-cert-file and --tls-private-key-file won't be possible!

For more information, please go to https://github.com/brancz/kube-rbac-proxy/issues/187

===============================================

It could be caused by https://github.com/search?q=repo%3Alatchset%2Ftang-operator+http%3A%2F%2F127.0.0.1%3A8080%2F&type=code

and source is https://github.com/brancz/kube-rbac-proxy/blob/master/cmd/kube-rbac-proxy/app/options/options.go#L163

Original issue:
latchset#268

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sarroutbi]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sarroutbi]

/remove-lifecycle stale