no default model created on microk8s bootstrap

[Tom Haddon]

Currently if you bootstrap on LXC juju will create two models for you, the controller model and a "default" model for workloads.

However, if you bootstrap on microk8s you get only the controller model and the following message:

```
Now you can run
        juju add-model <model-name>
to create a new model to deploy k8s workloads.
```

Wouldn't it be better to create and select a default model for the user to remove one step for them to have to do manually, and to be consistent with LXC?

[John A Meinel (jameinel)]

So this is only true on Juju <=2.9 and has never been true on Kubernetes.
Mark has asked that we make "add-a-model" a standard practice for users rather than doing it by default in bootstrap.
For 3.0 we are following the model for Kubernetes and after bootstrap you end up with a Controller but no Model, and will need to do an `add-model` post bootstrap.