And run juju bootstrap using that binary.
You also can likely access the binary inside the snap (without confinement) using:
/snap/juju/current/bin/juju bootstrap
(note /snap/bin/juju is the wrapper that sets up confinement and then executes the above binary)
Once bootstrapped, the controller should have a service account and be able to control the k8s cluster, and your juju client should be able to talk to that api.
Rebroadcast of the current workaround from public MM, by jameinel:
You should be able to either download a juju binary directly from: /launchpad. net/juju/ +download
https:/
(eg: https:/ /launchpad. net/juju/ 3.3/3.3. 0/+download/ juju-3. 3.0-linux- amd64.tar. xz
)
And run juju bootstrap using that binary.
You also can likely access the binary inside the snap (without confinement) using:
/snap/juju/ current/ bin/juju bootstrap
(note /snap/bin/juju is the wrapper that sets up confinement and then executes the above binary)
Once bootstrapped, the controller should have a service account and be able to control the k8s cluster, and your juju client should be able to talk to that api.