add-k8s doesn't allow me to specify a description

[Richard Harding]

When I show-clouds I get a list of clouds that can look a lot alike as everything k8s has the same description:

    juju clouds
    Only clouds with registered credentials are shown.
    There are more clouds, use --all to see them.

    Clouds available on the client:
    Cloud Regions Default Type Credentials Source Description
    aks-cluster 1 eastus k8s 0 local A Kubernetes Cluster
    aws 19 us-east-1 ec2 3 public Amazon Web Services
    gke-cluster 1 us-central1 k8s 0 local A Kubernetes Cluster
    google 21 us-east1 gce 1 public Google Cloud Platform
    guimaas 0 maas 1 local Metal As A Service
    k8s 1 localhost k8s 0 local A Kubernetes Cluster
    localhost 1 localhost lxd 1 built-in LXD Container Hypervisor
    microk8s 1 localhost k8s 1 built-in A Kubernetes Cluster

I have several that are "a kubernetes cluster" and if I had multiple on the same cloud backing (e.g. multiple clusters on ask) it would be great if I could add-k8s with a description argument to set the description to something unique.

I did check and verified I can manually edit the ~/.local/share/juju/clouds.yaml and add a description attribute to the cloud YAML and it'll update and show it. The only issue here is the lack of a CLI entryp oint to the data.

[Pen Gale (pengale)]

We technically have the same issue w/ lxd clusters.

I think that Rick's situation is a little unique, in that he was running a demo with a bunch of k8s clusters. I'm not sure that your typical operator would have access to that many k8s clusters.

otoh, a k8s cluster is a little more like a model than a cloud in some ways, so maybe it would be normal to have a lot of k8s clusters.

In any case, this is a valid ask. Going to confirm and mark as wishlist.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.