What is StackPointCloud?
StackPointCloud is a managed Kubernetes control plane to build cloud-native stacks on AWS, Google Cloud (GKE & GCE), Azure & DigitalOcean. StackPointCloud simplifies installation and aggregation of multiple Kubernetes clusters pretty much on any platform. Even if you are an expert, provisioning your own Kubernetes stack their easy to use interface and capabilities to centralize all your deployments in one place is compelling. StackPointCloud is free for the first 30 days and $49.95 month after for any number of Kubernetes clusters.
[Update] I have updated instructions on [11/16/17] to reflect improvements and changes StackCloudPoint implemented.
Minimum requirements for deploying your Kubernetes clusters on StackPointCloud:
- Amazon Web Services (AWS) account (Other major providers supported by StackPoint, but not covered in this article)
Start your StackPoint Trial
First, go to stackpoint.io and click on Launch a Cluster button to start your free trial.
Then choose your cloud provider. In this example, I will use AWS.
Configure Access to AWS
On the next screen, we need to configure our provider. You need to provide AWS Access Key ID and Secret Access Key and optionally your SSH Key.
If you don’t know where to find them, follow the instructions here to create your user.
Click on Add Credentials button.
After you add your credentials, click on Submit.
Configure K8s Cluster
On “Configure your cluster” page click the edit button on Distribution and choose Ubuntu 16.04 LTS.
Change the Cluster Name something meaningful like OpenEBS Demo.
I could separate my etcd into 3 nodes dedicated cluster, but for a functional demo hosting it on the same cluster works perfectly fine. You can leave all other option as default. Now click on Submit to create your cluster. This should take around 5-8 minutes to bring up one Master and two Workers Kubernetes Cluster.
[Update 11/16/17]: You can now deploy Kubernetes 1.8.3 on StackPointCloud. Make sure to enabled RBAC, and if you have done so, also keep RBAC enabled while deploying OpenEBS release later.
Import OpenEBS Helm Charts
Click on Solutions tab on the top of the screen and select Import Charts from the upper left.
Add the chart repo with the following details:
– name : openebs-charts
– type : packaged-charts
– repo url : https://openebs.github.io/charts/
Click on Review Repository.
Make sure Access Verified shows ok and click on Save Repository button to finish adding chart repo.
Adding OpenEBS to Your Kubernetes Cluster
First, make sure your cluster and all nodes are up.
On the Control Plane tab click on your cluster name OpenEBS Demo.
Once the Kubernetes cluster is up on AWS with functional Helm, click on the Solutions tab and Add Solution button.
Add the solution with the following details (If RBAC disabled):
– namespace : default
– values -> rbacEnabled : false
[Update 11/16/17]: StackPointCloud now supports Kubernetes deployment with RBAC. If have deployed your Kubernetes cluster with RBAC enabled, then keep the default
rbacEnabled : true
Click on Install to finally add OpenEBS into your cluster.
State field should be green after OpenEBS is successfully added.
Now your cluster is ready; you can run your workloads on openebs-standard storage class.
To confirm, click on K8s Dashboard. This will bring up your Kubernetes Dashboard UI in a new window. You should be able to find the openebs-standard option under Storage Classes.
I’ll cover some workload examples such as MongoDB, Percona, Cassandra and Postgres running OpenEBS on my next blogs (stay tuned).
Also published on Medium.