As discussed in https://bugs.launchpad.net/juju/+bug/1896819 they don't
really want Juju to be creating projects per model by default. Instead they
just wanted a clearer way that you could set the project when adding an LXD
cluster (so every model created with that credential would be in the same
project).
It should certainly be better documented, though.
On Mon, Oct 18, 2021 at 1:15 AM Harry Pidcock <email address hidden>
wrote:
> I'm also wondering if the mapping between k8s namespaces and models
> might make sense to replicate for LXD projects
>
> ** Changed in: juju
> Importance: Undecided => Medium
>
> ** Changed in: juju
> Status: New => Triaged
>
> ** Changed in: juju
> Milestone: None => 3.0.0
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1947443
>
> Title:
> model config project not documented
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1947443/+subscriptions
>
>
As discussed in https:/ /bugs.launchpad .net/juju/ +bug/1896819 they don't
really want Juju to be creating projects per model by default. Instead they
just wanted a clearer way that you could set the project when adding an LXD
cluster (so every model created with that credential would be in the same
project).
It should certainly be better documented, though.
On Mon, Oct 18, 2021 at 1:15 AM Harry Pidcock <email address hidden>
wrote:
> I'm also wondering if the mapping between k8s namespaces and models /bugs.launchpad .net/bugs/ 1947443 /bugs.launchpad .net/juju/ +bug/1947443/ +subscriptions
> might make sense to replicate for LXD projects
>
> ** Changed in: juju
> Importance: Undecided => Medium
>
> ** Changed in: juju
> Status: New => Triaged
>
> ** Changed in: juju
> Milestone: None => 3.0.0
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> model config project not documented
>
> To manage notifications about this bug go to:
> https:/
>
>