manual provider with floating IPs fails to properly add nodes
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_
---
also, when running 'kubectl get no -o yaml <node-name>' has no addresses field under status:
setting kubetlet-
This also allows for kube-proxy to start and thus for coredns to start.
affects: | charm-aws-iam → charm-kubernetes-worker |
description: | updated |
Changed in charm-kubernetes-worker: | |
status: | New → Confirmed |
upstream issue: https:/ /github. com/kubernetes/ kubernetes/ issues/ 54337