Workaround:
As as work-around I've lifted the current action's solution out of the main branch to a gist which lets an admin user run with `juju run`
I've provided an example run with the user "example". in this case, i'm targetting the application kubernetes-control-plane, but in some deployments it may be kubernetes-master
Workaround:
As as work-around I've lifted the current action's solution out of the main branch to a gist which lets an admin user run with `juju run`
I've provided an example run with the user "example". in this case, i'm targetting the application kubernetes- control- plane, but in some deployments it may be kubernetes-master
``` /gist.githubuse rcontent. com/addyess/ 681a2733987beef feb11ddcf3ff2d7 99/raw/ e1aab89c9779777 72583bb97e0ddc8 23303a273e/ lp-1956615. sh -O LP1956615.sh
wget https:/
USER="example" control- plane/leader -- bash -c "$(cat LP1956615.sh) $USER $GROUPS" control- plane/leader user-list -- wait control- plane/0: /home/ubuntu/ example- kubeconfig .
GROUPS=""
juju run -u kubernetes-
juju run-actions kubernetes-
juju scp kubernetes-
```