Listening Processes

In MetalK8s context several processes are deployed and they need to communicate with each other, sometimes locally, sometimes between machines in the cluster, or with the end user.

Depending on their roles, nodes must have several addresses available for MetalK8s processes to bind.

Listening Processes on Bootstrap Nodes

Address

Description

control_plane_ip:4505

Salt master publisher

control_plane_ip:4506

Salt master request server

control_plane_ip:4507

Salt API

control_plane_ip:8080

MetalK8s repository

control_plane_ip:8443

Control plane nginx ingress

Listening Processes on Master Nodes

Address

Description

0.0.0.0:6443

Kubernetes apiserver

127.0.0.1:7080

Apiserver proxy health check

127.0.0.1:7443

Apiserver proxy

control_plane_ip:10257

Kubernetes controller manager

control_plane_ip:10259

Kubernetes scheduler

Listening Processes on Etcd Nodes

Address

Description

127.0.0.1:2379

Etcd client

control_plane_ip:2379

Etcd client

control_plane_ip:2380

Etcd peer

127.0.0.1:2381

Etcd metrics

control_plane_ip:2381

Etcd metrics

Listening Processes on All Nodes

Address

Description

127.0.0.1:9099

Calico node

0.0.0.0:9100

Node exporter

127.0.0.1:10248

Kubelet health check

0.0.0.0:10249

Kubernetes proxy metrics

control_plane_ip:10250

Kubelet

0.0.0.0:10256

Kubernetes proxy health check