Securing Kubernetes API Server Health Checks Without Anonymous Access
How to disable anonymous auth globally but keep /livez, /readyz, and /healthz accessible Recently, a security-savvy colleague posed an interesting question: "Is it possible to disable anonymous access to the Kubernetes API server entirely, but still allow the /livez, /readyz, and /healthz endpoints to work?"
How to disable anonymous auth globally but keep /livez, /readyz, and /healthz accessible
Recently, a security-savvy colleague posed an interesting question: "Is it possible to disable anonymous access to the Kubernetes API server entirely, but still allow the /livez, /readyz, and /healthz endpoints to work?"
