You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace kube-rbac-proxy to ensure the same level of protection with controller-runtime feature
Utilise Controller-Runtime's WithAuthenticationAndAuthorization feature to protect the metrics endpoint. This approach provides access control, similar to the functionality of kube-rbac-proxy. kube-rbac-proxy image from gcr.io/kubebuilder/kube-rbac-proxy is deprecated and should no longer be used
More info: kubernetes-sigs/kubebuilder#3907
flag.StringVar(&metricsAddr, "metrics-bind-address", ":8080", "The address the metric endpoint binds to.")
107
+
flag.StringVar(&metricsAddr, "metrics-bind-address", "0", "The address for the metrics endpoint. "+
108
+
"The metrics server only runs with TLS protection (HTTPS) and will not be enabled without specifying tls-cert and tls-key. "+
109
+
"We recommend using port :8443, which is the target port mapped for the Service. "+
110
+
"If a different port is used, the Service configuration may need to be updated. "+
111
+
"If the value provided is '0', the metrics server will be disabled.")
101
112
flag.StringVar(&probeAddr, "health-probe-bind-address", ":8081", "The address the probe endpoint binds to.")
102
113
flag.StringVar(&caCertDir, "ca-certs-dir", "", "The directory of TLS certificate to use for verifying HTTPS connections to the Catalogd and docker-registry web servers.")
114
+
flag.StringVar(&certFile, "tls-cert", "", "The certificate file used for serving metrics contents over HTTPS. Requires tls-key.")
115
+
flag.StringVar(&keyFile, "tls-key", "", "The key file used for serving metrics contents over HTTPS. Requires tls-cert.")
0 commit comments