kube-rbac-proxy was only being used to protect the /metrics endpoint, which doesn't contain any sensitive data. Due to active development on this dependency, we kept running into situations where users would get alerts that kube-rbac-proxy was too far out of date. Rather than continually releasing new versions of the operator to address this, we're simply removing the dependency.
kube-rbac-proxy
was only being used to protect the/metrics
endpoint, which doesn't contain any sensitive data. Due to active development on this dependency, we kept running into situations where users would get alerts thatkube-rbac-proxy
was too far out of date. Rather than continually releasing new versions of the operator to address this, we're simply removing the dependency.Closes #62.