Open Ports and Services

The SMF uses different ports for communication purposes. The following table describes the default open ports and the associated services.

Open Ports and Services

Port

Service

Usage

22

SSH

SMI uses this TCP port to communicate with the virtual machines.

80

HTTP

SMI uses this TCP port for providing Web access to CLI, Documentation, and TAC.

443

SSL/HTTP

SMI uses this TCP port for providing Web access to CLI, Documentation, and TAC.

1434

ms-sql-m

SMI uses this UDP port to communicate with BIRD. BIRD is an open source BGP client that is used to exchange routing information between hosts.

6443

HTTP

SMI uses this port to communicate with the Kubernetes API server.

9100

jetdirect

SMI uses this TCP port to communicate with the Node exporter.

Node Exporter is a Prometheus exporter for hardware and OS metrics with pluggable metric collectors. It allows you to measure various machine resources such as memory, disk, and CPU utilization.

10250

SSL/HTTP

SMI uses this TCP port to communicate with Kubelet.

Kubelet is the lowest level component in Kubernetes. It is responsible for what is running on an individual machine. You can think of it as a process watcher like supervisor but focused on running containers. It has one job: given a set of containers to run, make sure they are all running.

10251

SMI uses this TCP port to interact with the Kube scheduler.

Kube scheduler is the default scheduler for Kubernetes and runs as part of the control plane. A scheduler watches for newly created Pods that have no node assigned. For every Pod that the scheduler discovers, the scheduler becomes responsible for finding the best Node for that Pod to run on

10252

apollo-relay

SMI uses this TCP port to interact with the Kube controller.

The Kubernetes controller manager is a daemon that embeds the core control loops shipped with Kubernetes. The controller is a control loop that watches the shared state of the cluster through the apiserver and makes changes attempting to move the current state towards the desired state.

10256

HTTP

SMI uses this TCP port to interact with the Kube proxy.

Kube proxy is a network proxy that runs on each node in your cluster, implementing part of the Kubernetes Service concept. Kube proxy maintains network rules on nodes. These network rules allow network communication to your Pods from network sessions inside or outside of your cluster.