Juju bootstrap failing with various Kubernetes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Thomas Miller |
Bug Description
From a prospective customer:
I tried to spin up a Juju controller on a remote/ local dev- Kubernetes cluster. I used “kind”, “minikube” and my private cluster. Everywhere the same problem. (I had a couple of different problems with juju, but in the end, it all boiled down to one crucial problem)
Steps to reproduce:
```
$ minikube start
$ # manually convert certificate-
$ juju add-k8s myMinikube
[…]
$ juju bootstrap myMinikube
[…]
Contacting Juju controller at 10.99.70.252 to verify accessibility...
$ # now [ctrl] + [c] does not work. Juju is not evaluating SIGKILL correctly.
```
What Juju now tries to do during the “bootstrap” command, is to connect to the ClusterIP of the controller. Usually a 10.x.x.x IP. This of course cannot work. A ClusterIP is only reachable from within the cluster.
I searched and searched… but I did not find a parameter to configure this.
Maybe there is a chance to get a quick tip what I did wrong here? As I said, either a “set x” by someone who knows of Juju – or we have a problem…
Changed in juju: | |
assignee: | nobody → Thomas Miller (tlmiller) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | Fix Committed → Fix Released |
There are 3 settings that are relevant:
* controller- external- name external- ips service- type
* controller-
* controller-
These are all allowed as part of "juju bootstrap --bootstrap-config controller- external- ips=XXX" , which will inform the Juju bootstrap process how the controller should be exposed to the rest of the world. This seems to be under documented, but is available in places like: /discourse. charmhub. io/t/juju- add-k8s- in-openstack- no-route- to-controller/ 3625/2
https:/