Port 10250 is the kubelet API on each Kubernetes node. The API server uses it to fetch logs, run kubectl exec and collect metrics. It should not be reachable from the public internet.
- Port
- 10250
- Protocol
- TCP
- Service
- Kubernetes kubelet API
- Expose to internet?
- No
Is port 10250 safe to open?
If the kubelet allows anonymous requests with AlwaysAllow authorisation, anyone who can reach 10250 can list pods and run commands inside any container on the node. Exposed kubelets have been widely used to deploy cryptominers.
How to secure Kubernetes kubelet API
- Set
--anonymous-auth=false(orauthentication.anonymous.enabled: falsein the kubelet config). - Use
--authorization-mode=Webhookso requests are checked by the API server. - Allow 10250 only from the control plane and monitoring systems.
- Disable the read-only port 10255 (
--read-only-port=0).
Check if port 10250 is open
Linux: what is listening on this port
sudo ss -tlpn | grep ':10250 'Windows (PowerShell): what is listening
Get-NetTCPConnection -LocalPort 10250 -State Listen | Select-Object LocalAddress, OwningProcess, @{n='Process';e={(Get-Process -Id $_.OwningProcess).Name}}From another machine: is it reachable
nc -zv HOST 10250
# or
nmap -p 10250 HOST
# Windows
Test-NetConnection HOST -Port 10250Test the Kubernetes kubelet API service itself
curl -sk https://HOST:10250/podsRestrict port 10250 in the firewall
Replace 10.0.0.0/8 with the network or address that needs access. Docker publishes container ports through its own iptables rules, which bypass ufw; bind published ports to 127.0.0.1 (-p 127.0.0.1:10250:10250) instead of relying on the host firewall.
ufw: allow only your private network, deny everyone else
sudo ufw allow from 10.0.0.0/8 to any port 10250 proto tcp
sudo ufw deny 10250/tcpfirewalld: allow one source network only
sudo firewall-cmd --permanent --remove-port=10250/tcp
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="10.0.0.0/8" port port="10250" protocol="tcp" accept'
sudo firewall-cmd --reloadiptables
sudo iptables -A INPUT -p tcp --dport 10250 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 10250 -j DROPWindows Firewall (PowerShell, as Administrator)
New-NetFirewallRule -DisplayName "Block 10250 from internet" -Direction Inbound -Protocol TCP -LocalPort 10250 -RemoteAddress Internet -Action BlockMonitor port 10250
Run a TCP port monitor against your public IP on port 10250: here, a failed connection is the healthy result, so you know the firewall is still doing its job. On Linux, the Statance agent also reports every listening port on the server. TCP port monitoring.
Related ports
| Port 6443 | Kubernetes API server | High risk |
| Port 2379 | etcd (client API) | Critical risk |
| Port 2375 | Docker Engine API (unencrypted) | Critical risk |
FAQ
What is port 10250 used for?
Port 10250 is the kubelet API on each Kubernetes node. The API server uses it to fetch logs, run kubectl exec and collect metrics.
Is it safe to open port 10250?
Not to the public internet. If the kubelet allows anonymous requests with AlwaysAllow authorisation, anyone who can reach 10250 can list pods and run commands inside any container on the node. Exposed kubelets have been widely used to deploy cryptominers.
Is port 10250 TCP or UDP?
Kubernetes kubelet API uses TCP on port 10250.
How do I check if port 10250 is open?
On the server, run sudo ss -tulpn | grep ':10250 ' (Linux) or Get-NetTCPConnection -LocalPort 10250 (Windows) to see what is listening. From another machine, run nc -zv HOST 10250 or Test-NetConnection HOST -Port 10250.
Know the moment a port stops answering.
TCP, HTTP, DNS and SSL checks from six regions, plus server metrics from a one-line agent.