Join us

Why You Should Disable Your Unauthenticated Read-only Ports On GKE Kubelet Servers

Why You Should Disable Your Unauthenticated Read-only Ports On GKE Kubelet Servers

Google alerted GKE users about an unauthenticated "read-only" port 10255 in the Kubelet server that could lead to data leaks. Google plans to phase out this port in GKE version 1.32 and future releases, but current clusters need manual intervention to disable it. Orca's scans reveal that 87% of organizations running GKE have at least one open port 10255, urging administrators to disable it for enhanced security.


Let's keep in touch!

Stay updated with my latest posts and news. I share insights, updates, and exclusive content.

Unsubscribe anytime. By subscribing, you share your email with @faun and accept our Terms & Privacy.

Give a Pawfive to this post!


Only registered users can post comments. Please, login or signup.

Start writing about what excites you in tech — connect with developers, grow your voice, and get rewarded.

Join other developers and claim your FAUN.dev() account now!

Avatar

The FAUN

FAUN.dev()

@faun
The FAUN watches over the forest of developers. It roams between Kubernetes clusters, code caves, AI trails, and cloud canopies, gathering the signals that matter and clearing out the noise.
Developer Influence
3k

Influence

302k

Total Hits

3712

Posts