search

Wrong Interface/IP Assigned For Kube-apiserver

hashtag
Problem

If the user defines a custom interface in the /var/opt/pf9/kube_interface_v4 interface file, it is being picked up correctly for the ETCD and all the other components except the Kube-API server.

# cat /var/opt/pf9/kube_interface_v4
V4_INTERFACE enp1s0

# ip r | grep enp1s0
172.22.216.0/22 dev enp1s0 proto kernel scope link src

The default kubernetes service is pointing to the incorrect interface of the nodes.

# kubectl get ep
NAME                   ENDPOINTS                             AGE
kubernetes192.168.122.108:443,192.168.122.190:443,192.168.122.39:443 25d

API server is responding and as per the configuration, it is listening on all the interfaces as per the bind address of 0.0.0.0.

hashtag
Environment

  • Platform9 Managed Kubernetes - v5.6 and Higher

hashtag
Answer

  • An internal Jira PMK-6275 has been created and Platform9 Engineering team is working on it.

  • The fix is available in PMK-5.10 and higher release.

PreviousFalse Alerts Generated by Alertmanager for KubePersistentVolumeErrorsNextKubectl Commands Throwing Error Metrics Server Currently Unable to Handle Requests

Last updated