manual provider with floating IPs fails to properly add nodes

Bug #1853187 reported by Jeff Hillman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Worker Charm
Triaged
High
Unassigned

Bug Description

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.

Tags: cpe-onsite
Jeff Hillman (jhillman)
affects: charm-aws-iam → charm-kubernetes-worker
Jeff Hillman (jhillman)
description: updated
George Kraft (cynerva)
Changed in charm-kubernetes-worker:
status: New → Confirmed
Revision history for this message
George Kraft (cynerva) wrote :
Changed in charm-kubernetes-worker:
importance: Undecided → High
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.