-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
analyzer: make sure there's a valid interface that kubernetes can use #1536
Comments
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 |
@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:The text was updated successfully, but these errors were encountered: