Urgent.News

What's breaking now, across hundreds of outlets.

Tech

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.

Read the original at dev.to →

Report a problem with this story

More in Tech

iPad Pro vs MacBook Air vs Surface Pro: Best Dev Machine?

Every year, the same dream resurfaces: What if I could ditch the heavy laptop and just code on a tablet? And every year, reality bites. But 2026 feels different.

  • MacBook Air remains best portable dev machine in 2026
  • iPad Pro offers lighter weight and improved portability
  • Surface Pro 11 provides genuine usability for Windows-first devs

Short Stints & Contract Hops: Framing a Choppy Timeline

The resume that worries people most in this series is not the one with a gap. It is the one with too many entries. Eight months at a startup that ran out of money.

  • Multiple short stints at startups and contracts create choppy timeline
  • Normalize dates using consistent format for ATS parsing
  • Group contract work under one umbrella entry with neutral reason

Trap Streets for Code: How Mapmakers Caught Copiers, and How I Do It in Git

In the 1920s, two mapmakers at General Drafting, Otto G. Lindberg and Ernest Alpers, put a town on their map of New York that didn't exist.

  • Mapmakers used trap streets in 1920s to catch map copiers
  • TrapR tool uses markers, canaries, fingerprints to detect code copiers
  • Multi-layered approach helps monitor and protect code in Git repositories

More from Saturday 21 November →