Complete User guide for Kubera

Setup Kubera Director

Kubera Director is a SaaS portal that enables the DevOps and Administrators to connect their Kubernetes clusters for centralized monitoring, Data Migration as a Service (DMaaS), ChatOps and obtaining support from MayaData.

NOTE: If you have already logged into MayaData Portal, skip to Step 3

STEP 1:

Click here to get directed to Kubera Director.

User can signup using any of the three options:   

STEP 2: 

UPDATE YOUR PROFILE:

1. The Email ID field will be immutable and will contain the registered Email ID.

2. Add your Phone Number.

3. Next, add your Company Name.

4. Next, add your Role .

5. Click on Submit.

STEP 3:

ADD YOUR PROJECT NAME

Provide the desired name for the project in the box and click on continue.

STEP 4:

Connect your K8s cluster.

1. Select the correct details according to whether the cluster used is managed or On-Premise or Others.

2. Provide a cluster name.

The Cluster cannot be re-named later.

3. Click on connect.

STEP 5:

Copy and execute the lines of code visible in the Pop-Up screen on your command prompt which is connected to your cluster.

You will be redirected to Kubera Director Dashboard, now you are all set to monitor your clusters.

Installing OpenEBS

Installing OpenEBS OpenEBS provides block volume support through the iSCSI protocol. Therefore, the iSCSI client (initiator) presence on all Kubernetes nodes is required. Choose the platform below to find the steps to verify if the iSCSI client is installed and running or to find the steps to install the iSCSI client.
Linux platforms Installation of the iSCSI initiator service and tools depends on your host O/S or the kubelet container. You can follow the below steps for installation/verification of the required packages. It is a mandatory step to verify the iSCSI services and make sure that it is running on all the worker nodes. OpenEBS uses iSCSI protocol to connect to the block volumes. To get iSCSI initiator installed please follow the steps at iSCSI-install

Steps for OpenEBS installation

OpenEBS can directly be installed using the Kubera Director UI. 

The overall installation process is divided into two types:

1. Basic: Basic Installation is recommended in scenarios where OpenEBS needs to be deployed using the default values.
2. Advanced: Advanced Installation is recommended in cases where OpenEBS needs to be installed with customized values.

STEP 1:

Connect your cluster to Kubera Director. To know the detailed steps click here.

STEP 2:

Once the cluster is connected, to install OpenEBS click on OpenEBS on the left side-bar.

STEP 3:

Next, You can choose installation type as Basic or Advanced based on your requirement. 

If you want to setup OpenEBS with default settings, select Basic Installation else to customize resource limits, node selection and Node Disk manger before installation, select Advanced Installation.

Basic installation provides you with an uneditable YAML. All the values have been set to default and OpenEBS gets deployed in the openebs namespace.
To deploy, click on Deploy OpenEBS.


The installation might take a few minutes. Once the installation is complete you'll have the following screen displaying all the Installed OpenEBS components.


Click on continue, this redirects you to the page displaying the status of Control Plane Components.
OpenEBS is now successfully installed on your cluster.

NOTE:
Scheduling Control Nodes and Data Nodes are the compulsary fields, these need to be selected otherwise the pods end up in pending state as they do not get a node to be scheduled on. All other fields can be customized as per your requirement. In case no values are specified OpenEBS get installed with default values.

1. Under Start Installation specify the Namespace, Default Directory and Docker registry for OpenEBS Installation.
   
   
   

   Note:
   

   • While specifying the namespace, ensure that it must contain a min of 6 characters without spaces or symbols.
   • While specifying the namespace, you can specify any namespace. In case the specified namespace does not exis, it gets created automatically.

2. Next, Specify your resource limit. You can choose ones of these options available based on the size of the application or you can provide some custom values.
   
   
3. Next, Select the nodes where Control Plane components will get scheduled.
   
   
4. Similarly, select the nodes where the Data Plane components have to be scheduled.
   
   
5. Next, segregate the Disk Filters under Include or Exclude.
6. OpenEBS now supports MayaStor. To include MayaStor installation, select the slider button as shown in the image.
   
   To know more about MayaStor click here.
7. Once everything is done, the customized YAML gets displayed. Click on Deploy OpenEBS to install OpenEBS.
   
   

Installation may take a few minutes.

In case OpenEBS installation fails, you can choose to abort installation process. Aborting stops installation and removes all the components that may have been installed.



After aborting you may retry installation or in case of any further queries feel free to contact our support. 

Provisioning a cStor pool

This feature is supported for OpenEBS versions >= 1.10.0 , OpenEBS can either be installed using Director or can be done manually. If OpenEBS is installed manually, ensure that the CSPC operator is installed.

CSPC is a new schema for cStor pool provisioning that refactors the code to make the cStor a completely pluggable engine into OpenEBS. The new schema also makes it easy to perform day 2 operations on cStor pools.

STEP 1:

On the left sidebar click on  Storage Pools under Management and then click on create new pool.

STEP 2:

1. Provide a name for your CSPC and select the RAID type. A set of recommendations will be displayed grouped-by device-type and node-names. While specifying these, the following things should be taken into consideration
   • While selecting the CSPC type please note RaidZ and RaidZ2 supports only the default configuration, i.e, 2+1 for RaidZ and 4+2 for RaidZ2.
   • The number of nodes to be selected for the pool depends upon the required replication factor, i.e if the number of replicas needed are three, then choose three nodes for the pool.
   
   If the block devices are attached to the nodes but are still not present in recommendations please check our troubleshooting document.
2. Select the device-type from the drop-down to view the node-based recommendations for that type.

NOTE:Only raw, unformatted and unclaimed devices are considered for displaying recommendations.

While selecting nodes you can also view the set of disks that are grouped or ungrouped. Select the nodes and click on Generate cluster config.

This generates a summary of the choices that had been selected and an autogenerated YAML based on the previous selections.

Click on Create. Creation of StoragePools might take few minutes. Once created, they can be viewed from View Created Pool button at bottom right corner of the screen.

The list of pools and the associated details can be viewed from Storage Pool under Managment section present in the left sidebar.

The created cStor pool can be used to provision an application, this involves few manual steps. To know the steps click here.