Right now when you have a running cluster and want to use it on another machine you need to copy the uncloud.yaml config over or cut and paste into your local config.
(of course you also need fiddle with ssh keys, but assume that is taken care off - although having a command that upload a key and places it in ~/.ssh/config for the uncloud user could be handy as well)
A good place is likely uc ctx, but uc machine ... already does things with ssh and a lot of things already live there, like other cluster commands.
Proposing to add a uc machine context that adds the cluster context to your local context:
-c can be reused, this will be the name of the context, default-N otherwise
- The
[schema://]USER@HOST[:PORT will be reused for a machine connections
Note sure if the machines dns names are actually stored in the cluster, otherwise it will be tricky to get those.
Right now when you have a running cluster and want to use it on another machine you need to copy the uncloud.yaml config over or cut and paste into your local config.
(of course you also need fiddle with ssh keys, but assume that is taken care off - although having a command that upload a key and places it in ~/.ssh/config for the uncloud user could be handy as well)
A good place is likely
uc ctx, butuc machine ...already does things with ssh and a lot of things already live there, like other cluster commands.Proposing to add a
uc machine contextthat adds the cluster context to your local context:-ccan be reused, this will be the name of the context, default-N otherwise[schema://]USER@HOST[:PORTwill be reused for a machine connectionsNote sure if the machines dns names are actually stored in the cluster, otherwise it will be tricky to get those.