cancel
Showing results for 
Search instead for 
Did you mean: 
vsolodkyi
Sisense Team Member
Sisense Team Member

The Linux version of Sisense uses Kubernetes to orchestrate containers which run our services. Kubernetes has many options for provisioning and managing clusters. Starting from version L2022.8 Sisense moved from Kubespray deployments to RKE deployments. In this article we will review the main difference between these two types of deployments. 

Kubespray is a composition of Ansible playbooks, inventory, provisioning tools, and domain knowledge for generic OS/Kubernetes clusters configuration management tasks. Kubespray uses kubeadm in the background and is managed by ansible playbooks. It uses Terraform modules as well. 

Kubespray is very easy to customize because of Ansible, however installation takes a long time to execute changes because Ansible works sequentially. It then becomes hard to troubleshoot because of unexpected errors within the same situation on different environments.

RKE (Rancher Kubernetes Engineis a new CNCF-certified Kubernetes distribution that reinstalls and manages Kubernetes components as docker containers Kubernetes clusters. It works on bare-metal and virtualized servers. RKE could be installed on cloud-managed platforms like EKS or AKS which makes this type of deployment more flexible. 

RKE solves the problem of installation complexity, a common issue in the Kubernetes community. With RKE, the installation and operation of Kubernetes is both simplified and easily automated, and it’s entirely independent of the operating system and platform you’re running - RKE installation could be easily managed by a single yaml file. As long as you can run a supported version of Docker, you can deploy and run Kubernetes with RKE. Although RKE is a newer solution compared to the others, it is well documented and easy to troubleshoot. 

Here is an overall comparison table of RKE and Kubespray:

RKE

 

Kubespray

 

Pros

Cons

Pros

Cons

Works on bare-metal, VMs or managed Kubernetes like EKS, AKS and GKE

New deployment solution for management and installation

Easy customization with Ansible

Installation takes long time because Ansible works sequentially

Easy to automate, install and troubleshoot

 

Support for custom Kubernetes add-ons

Hard to troubleshoot

Well-documented

     

In summary, RKE provides a more simplified and flexible installation process. RKE also manages tools for Kubernetes clusters compared to Kubespray which makes the installation process more understandable and easier to troubleshoot. Also, RKE could be installed on cloud-managed Kubernetes (however we are still recommending using provisioner to install Sisense in EKS, AKS, or GKE)  

The Linux version of Sisense started to use RKE as a deployment tool from the L2022.1 release. Kubespray will be deprecated from the upcoming L2022.8 version. 

Since Kubespray and RKE are different types of Kubernetes deployments, the only way to migrate is via reinstallation, which is described in this article. This process could be described in 4 steps: 

  1. Create a backup of previous Kubespray environment 
  2. Uninstall Kubespray environment
  3. Install Sisense with a RKE deployment
  4. Restore backup
Version history
Last update:
‎08-17-2022 06:18 AM
Updated by:
Community Toolbox

Recommended quick links to assist you in optimizing your community experience:

Need additional support?:

Community Support Request