add-k8s should be more flexible in loading config

Bug #1768837 reported by Cory Johns on 2018-05-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Yang Kelvin Liu

Bug Description

It seems that `juju add-k8s` only supports reading ~/.kube/config and has no support for selecting which cluster from that file (it can contain multiple).

The following options should be added:

  * Option to specify config file location
  * Option to read config file from stdin, for use with `kubectl config view --raw | juju add-k8s`
  * Option to select context from config by name, defaulting to the `current-context` field of the config

John A Meinel (jameinel) on 2018-05-03
Changed in juju:
importance: Undecided → High
status: New → Triaged
tags: added: caas k8s
Ian Booth (wallyworld) wrote :

The add-k8s command does honour the KUBECONFIG env var for determining the file location.

Changed in juju:
milestone: none → 2.4-beta2
assignee: nobody → Yang Kelvin Liu (kelvin.liu)
Changed in juju:
milestone: 2.4-beta2 → none
Ian Booth (wallyworld) on 2018-05-11
Changed in juju:
milestone: none → 2.4-rc1
Cory Johns (johnsca) wrote :

Good to know about KUBECONFIG. It should be mentioned in `juju add-k8s --help`

Ian Booth (wallyworld) on 2018-05-15
Changed in juju:
status: Triaged → In Progress
Ian Booth (wallyworld) on 2018-05-18
Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers