Juju 2.7-rc2, --client-only flag not implemented in add-k8s
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Anastasia | ||
2.7 |
Fix Released
|
High
|
Anastasia |
Bug Description
Hello,
I am testing the juju 2.7-rc2 snap, and I found an issue:
First of all, if I add the k8s cloud with the following command, it doesn't work:
davigar15@
This operation can be applied to both a copy on this client and to the one on a controller.
Do you want to add k8s cloud k8s to:
1. client only (--client)
2. controller "aws-osm-ha" only (--controller aws-osm-ha)
3. both (--client --controller aws-osm-ha)
Enter your choice, or type Q|q to quit: ERROR EOF
With the --local flag it works, BUT, in the `juju add-k8s --help` command, it shows that the --local is deprecated:
```
--local (= false)
DEPRECATED (use --client-only): Local operation only; controller not affected
```
It says to use --client-only instead, and this is what happens when doing that:
```
davigar15@
ERROR option provided but not defined: --client-only
```
Using --client instead of --client-only is working:
```
davigar15@
k8s substrate "microk8s/
You can now bootstrap to this cloud by running 'juju bootstrap k8s'.
```
I don't know if it is an issue in the help of the add-k8s, or an alias is missing.
Thanks,
David
Changed in juju: | |
milestone: | 2.7.1 → 2.8-beta1 |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Ups, it was me @davigar15