What is StackPointCloud Trusted Charts?
StackPointCloud (SPC) introduced a concept of Trusted Charts, a list of validated Helm Charts provided by its partners to quickly spin up a solution in a Kubernetes cluster. Helm Charts helps you define, install, and upgrade even the most complex Kubernetes application.
Previously, I wrote about few different ways of getting OpenEBS up and running on different cloud vendors. Using Helm Chart is one of the available options to deploy OpenEBS. OpenEBS Helm Charts were available since v.5.0 both on Github and as a packaged chart. Recently SPC included OpenEBS into their Trusted Charts repo and made it one-click easy for its customers.
SPC Trusted Charts currently offer 23 solutions including databases, CI/CD, monitoring, storage and ingress solutions. Here is the list of Trusted Charts:
I’ll go through the quick steps of deploying OpenEBS.
Minimum requirements for deploying your Kubernetes clusters on StackPointCloud:
Cloud Provider Account
Deploy a New Kubernetes Cluster
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 Digital Ocean.
Configure Access to Digital Ocean
On the next screen, we need to configure our provider. You need to provide Digital Ocean API Token and optionally your SSH Key.
Click on Add API Token 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.
Leave everything else as default and click on Submit.
In about 10-15 minutes you will get your new cluster deployed.
Adding OpenEBS to Your Kubernetes Cluster
First, make sure your cluster and all nodes are up.
On the Control Plane tab click on your recently created cluster.
Once the Kubernetes cluster is up on Digital Ocean with functional Helm, scroll down to the Solutions tab and click on Add Solution button.
Click on Add Solutions, and select Trusted Charts.
From the list above select OpenEBS.
Release Name is randomly generated every time. If you want to use OpenEBS example workloads provided in OpenEBS repos without any modification then use
default as NameSpace. Otherwise, you need to modify the namespace for workloads you deploy and make sure to use the same name.
Click on Install to deploy OpenEBS on your cluster.
Note: Default settings assume that RBAC is enabled. If you disabled RBAC while you are configuring your provider previously then set
rbacEnable: false otherwise use default values.
State field should be green after OpenEBS is successfully added.
Now your cluster is ready; you can run your workloads on [cci]openebs-standard[cci] and other predefined storage classes.
To confirm, click on Kubernetes Dashboard. This will bring up your Kubernetes Dashboard UI in a new window. You will find all predefined OpenEBS Storage Classes here under Storage Classes section.
Now you are ready to deploy your stateful workloads.
Also published on Medium.