add-k8s should be more flexible in loading config
Bug #1768837 reported by
Cory Johns
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
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
| Changed in juju: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| tags: | added: caas k8s |
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| milestone: | none → 2.4-beta2 |
| assignee: | nobody → Yang Kelvin Liu (kelvin.liu) |
| Changed in juju: | |
| milestone: | 2.4-beta2 → none |
| Changed in juju: | |
| milestone: | none → 2.4-rc1 |
Revision history for this message
| Cory Johns (johnsca) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → In Progress |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The add-k8s command does honour the KUBECONFIG env var for determining the file location.