Open adamancini opened 2 months ago
Per https://kubernetes.io/docs/concepts/services-networking/service/#custom-endpointslices we should consider interfaces in both loopback and link local ranges to not be valid for install.
Also, this is relevant for kubernetes
in general not just for kubeadm
based installs. I've updated the title to that effect.
@diamonwiggins thanks for tracking that down
If we improve this we should be sure to update the Embedded Cluster spec when it's available: Ref https://github.com/replicatedhq/embedded-cluster/pull/579/files
Describe the rationale for the suggested feature.
An end user may try to implement airgapping by removing the primary interface of the host or by removing routes from the routing table - this may break CNI if there is no interface to use to build a bridge for flannel.
Describe the feature
Detect if there is a valid interface that
kubeadm init
can use for building CNI.Describe alternatives you've considered
something along the lines of what happens during
kubeadm init phase preflight
which can generate errors like from this interface list: