Kubelet readOnlyPort is an unauthenticated cluster inventory path
Kubelet readOnlyPort is an unauthenticated cluster inventory path The kubelet has a read-only port that serves requests with no authentication or authorization. The kubelet configuration documents the setting as readOnlyPort , and the command-line reference says to set it to 0 to disable it. A cluster that leaves this port reachable gives an unauthenticated caller a path to kubelet status and pod…
The kubelet has a read-only port exposed for serving status and pod metadata. By default, authentication and authorization are not enforced on this port, making it an unauthenticated inventory path of the cluster. This configuration detail is documented in the kubelet settings, but often overlooked during cluster hardening. The read-only port provides valuable reconnaissance information on pod names, namespaces, container images, node details, and more.
This seemingly harmless port can expose the shape of a production environment to anyone with access. The Kubernetes project explicitly recommends disabling this unauthenticated read-only port as part of cluster security best practices. A security review must inspect every node's kubelet configuration, not just the API server settings.
Even if the configuration file sets the readOnlyPort to zero, a stale command-line override could still enable the port. Verification requires checking the effective configuration across all nodes, not just one. Once remediated, confirm the change has taken by ensuring the port is no longer listening and the secured endpoint still has the intended authenticators.
Rewritten by urgent.news; may contain errors — check the original.