| 2019-11-19 19:44:24 |
Jeff Hillman |
description |
juju 2.6.10
k8s 1.16.2
Using Openstack with manual provider (due to security issues raised by customer for default security rules created by juju with openstack as provider). The nodes are being added to juju via the floating IP (either direct IP or dns entry pointing to floating IP)
The cluster deploys but kube-proxy fails to start, which in turn causes coredns to not start.
There is an error coming from the kubelet daemon that says:
---
kubelet_node_status.go:566 Failed to set some node status fields: failed to validate nodeIP: node IP: "<floating IP>" not found in the host's network interfaces
---
also, when running 'kubectl get no -o yaml <node-name>' has no addresses field under status:
setting kubetlet-extra-args="node-ip=" causes the address to now show up and it shows the private tenant address.
This also allows for kube-proxy to start and thus for coredns to start. |
juju 2.6.10
k8s 1.16.3
Using Openstack with manual provider (due to security issues raised by customer for default security rules created by juju with openstack as provider). The nodes are being added to juju via the floating IP (either direct IP or dns entry pointing to floating IP)
The cluster deploys but kube-proxy fails to start, which in turn causes coredns to not start.
There is an error coming from the kubelet daemon that says:
---
kubelet_node_status.go:566 Failed to set some node status fields: failed to validate nodeIP: node IP: "<floating IP>" not found in the host's network interfaces
---
also, when running 'kubectl get no -o yaml <node-name>' has no addresses field under status:
setting kubetlet-extra-args="node-ip=" causes the address to now show up and it shows the private tenant address.
This also allows for kube-proxy to start and thus for coredns to start. |
|
