juju fails to respect kubeconfig insecure-skip-tls-verify
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Ian Booth |
Bug Description
I have a kubeconfig:
```
apiVersion: v1
clusters:
- cluster:
server: https:/
insecure-
name: minikube
```
But running `juju add-k8s myk8scloud` disregards the instruction to not do TLS verification:
```
luke@light:
Since Juju 2 is being run for the first time, downloaded the latest public cloud information.
This operation can be applied to both a copy on this client and to the one on a controller.
No current controller was detected and there are no registered controllers on this client: either bootstrap one or register one.
ERROR Juju needs to query the k8s cluster to ensure that the recommended
storage defaults are available and to detect the cluster's cloud/region.
This was not possible in this case so run add-k8s again, using
--storage=<name> to specify the storage class to use and
--cloud=<cloud> to specify the cloud.
: cannot determine cluster region: listing nodes: Get "https:/
```
Juju should respect the kubeconfig parameter and not do TLS verification if it's told not to.
Changed in juju: | |
milestone: | none → 2.8.7 |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju: | |
assignee: | nobody → Ian Booth (wallyworld) |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 2.8.7 → 2.8.8 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
milestone: | 2.8.8 → 2.8.7 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
PR up at https:/ /github. com/juju/ juju/pull/ 12378