Allow creating new projects without setting up Kubernetes

[vkorenev]

Is your feature request related to a problem? Please describe.
I want to create a new Cloudstate service. However, the following command fails because there are no templates in ~/.cloudstate:

$ cloudstate create --name=inventory --profile=kotlin --registry=docker.io --tag=0.1
Creating user function project: "inventory"
Using profile: "kotlin"
You must first boot CloudState with cloudstate --init. See cloudstate --help for help
Ok(())

However, cloudstate init tries to perform some initialization on Kubernetes cluster and then fails:

$ cloudstate init
😉 Creating CloudState namespace...
Error from server (Forbidden): namespaces is forbidden: User "volodymyr.koreniev@yoppworks.com" cannot create resource "namespaces" in API group "" at the cluster scope
😻 Success on create CloudState namespace
🚀 Initializing CloudState operator...
Error from server (Forbidden): error when retrieving current configuration of:
Resource: "apiextensions.k8s.io/v1beta1, Resource=customresourcedefinitions", GroupVersionKind: "apiextensions.k8s.io/v1beta1, Kind=CustomResourceDefinition"
Name: "statefulstores.cloudstate.io", Namespace: ""

Describe the solution you'd like
I think that the cloudstate-cli tool should allow creating a new project even if I have not set up Kubernetes cluster for deploying Cloudstate service yet. Probably, cloudstate create should fetch templates if that has not been done yet.

[sleipnir]

I believe that this workflow can really be improved. As many later commands depend on an active cluster (which is a Minikube) then the init command already performs all the necessary setup so that everything works later. But this is good in the happy path and terrible way when not. I will treat this as a feature request and prioritize it to enter a new version in the next few days.

[vkorenev]

Actually, I'm using Lightbend Cloudstate cluster, so I have everything set up for deployment of Cloudstate services. But I don't need (and I don't even have permissions) to create namespaces, set up the Cloudstate operator, etc.

[sleipnir]

Yes, in fact this Cloudstate Community CLI is to be used for other use cases. So it makes sense, in this case, to separate the creation of templates from the deployment lifecycle and make them independent. The Lightbend cluster already provides all the necessary kubernetes abstractions in a self-managed manner. This CLI was created before the Lightbend Cluster project was released for testing and there has not been much synergy between the two projects so far. But I believe that both are complementary and after correcting some of the problems, perhaps they can be used together in a complementary way.