why the kubernetes pod expose some extra port when scanning

2/14/2020

When I using this command to scan my CoreDNS service in some pod:

nmap -sS -p 0-9999 -v 10.254.0.2

It shows the result like this(part):

Host is up (0.000087s latency).
Not shown: 9983 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
53/tcp   open  domain
80/tcp   open  http
111/tcp  open  rpcbind
222/tcp  open  rsh-spx
443/tcp  open  https
801/tcp  open  device
802/tcp  open  mbap-s
3306/tcp open  mysql
3309/tcp open  tns-adv
4431/tcp open  wspipe
4432/tcp open  l-acoustics
5000/tcp open  upnp
8082/tcp open  blackice-alerts
8083/tcp open  us-srv
8090/tcp open  opsmessaging
9153/tcp open  unknown

with this result make me confusing,the 53 \9153 port is expose by myself,and the 22\80 port maybe exposed by system,I understand.But I am very sure it has no mysql 3306 port in my pod,and I am not exposed this.How to explain the result?My CoreDNS port really have this port in using?

-- Dolphin
kubernetes

0 Answers