Skip to content

kube-rbac-proxy reports deprecation of insecure listen address

Summary

I see a deprecation warning from kube-rbac-proxy when the GitLab Controller Pod starts up.

Steps to reproduce

  1. Deploy Operator version 0.21.2
  2. Watch the logs from the Operator Controller Pod

Configuration used

Plain installation using task build_operator; task deploy_operator.

Versions

  • Operator: v0.21.2
  • Platform:
    • Cloud: GKE
  • Kubernetes: (kubectl version)
    • Client: v1.25.3
    • Server: v1.26.5

Relevant logs

==== 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

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