Open BaudouinH opened 3 years ago
ritusood
commented
3 years ago Currently we don't support specifying namespace when creating level-0 logical cloud. What will be the priority for you for this feature? We can extend the existing functionality of creating a logical cloud without specifying any user name, user permissions or quotas. This can create a namespace across all clusters.
BaudouinH
commented
3 years ago I am not sure of the priority of such feature, on the one hand, not being able to deploy to a namespace different from "default" on a level-0 logical cloud is an important shortcoming for level-0 logical clouds. On the other hand, you can achieve that with level-1 logical cloud, which might be a more sensible way of managing clusters than level-0 logical clouds.
igordcard
commented
3 years ago Hi @BaudouinH, yes, currently EMCO assumes "default" as the namespace for L0 (we plan on making this more flexible, in the future,.. or at least transparently pass over the namespace from the kubeconfig specified when creating the clusters). The end goal of L0 is to give full access to the cluster (think admin/infra owner), not just a particular namespace. We are working to achieve the right layering.
Hello,
I'm currently using EMCO to deploy Helm charts on a level-0 logical cloud.
From what I understood, a level-1 logical cloud has only one namespace (consistent across multiple clusters), so the apps deployed on this level-1 logical cloud will be deployed on this namespace.
However, with a level-0 logical cloud, I haven't found how to specify the deployment's namespace ? (Something similar to the --namespace flag of an Helm release).
Is it currently possible to specify a specific namespace when deploying on a level-0 logical cloud ? If so, does it need to be created beforehand (or is there an equivalent of Helm's --create-namespace)?