no way to 'ssh controller' on kubernetes models
Bug #1925967 reported by
John A Meinel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
We enabled support for 'juju ssh myapp/0' for kubernetes models.
However, the standard pattern of "juju ssh -m controller 0" to get to the controller doesn't work on K8s, because it doesn't "have machines" and requires that you ssh to a unit. But there isn't a unit here.
This may be easier once we model controllers as apps, but since that still isn't present in 2.9 we should have some sort of workaround. (And you can't use the machine trick of deploying something 'to the same machine' because k8s doesn't allow that, either.)
To post a comment you must log in.
This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.