Client-server model

Before I began working on snow, I did my best to research alternatives. I, too, came across exoframe.

The benefits of a client-server model look appealing: instead of needing this basket of installed system dependencies, you instruct the server via REST endpoints to create deployments, update deployments, etc. If we were to explore such an approach, you'd still need kubectl on your system to initially authenticate to install the server component.

I considered this, but for an 0.x release, I wouldn't have the bandwidth to deliver it.

Dashboard

Kubernetes ships a feature called the Web UI (Dashboard): https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/

• A UI dashboard for only viewing system state is one thing. Modifying the state of the system is another: we'd want to think about the security implications there. If your dashboard were to be compromised, your app could be taken down.
• The Kubernetes dashboard is probably a little too powerful for people using snow. As you mention, we'd probably want our own (more limited) dashboard -- a GUI that had parity with the snow CLI commands. It would be fun to build such a thing. So many ideas, so little time! 😅
• The dashboard could be built independently of the client/server model functionality (above).

Takeways

A better ecosystem surrounding snow would facilitate ease-of-use.

• @snowjs/cli - Got this
• @snowjs/dashboard - Web UI for cluster
• @snowjs/server - REST interface for managing cluster

Taken to the next level:

• @snowjs/app - Mobile client shipped to the app stores

Great roadmap :) I totally understand that this is to much for a 0.x release.

I am happy to help in building such thinks. Unfortunately, I have no clue about kubernetes. If there is anything besides that, let me know how to help.