Deploy Sisense on EKS 1.22 with RKE

[Cleber]

Hello Team,

We recently upgraded the Sisense from L2022.06.0 to L2022.11.0, on EKS 1.22.

I am trying to understand the migration process from Kubespray to RKE.

On versions L2022.11.0 and L2023.3.1, inside the links below, both contain a folder called "kubespray", which I believe still uses Kubespray. If, Kubespray is already deprecated, why do we still have it on the latest package file?

https://data.sisense.com/linux/sisense_linux_L2022.11.0.tar.gz

https://data.sisense.com/linux/sisense_linux_L2023.3.1.tar.gz

For a brand new EKS Cluster, what is the URL to download to the package to install Sisense L2023.01.0 already with RKE? So, we can avoid the manual steps to migrate the Kubespray to RKE.

Also, it possible, could you please provide me an URL from Sisense where I can find all installation packages available? Inside the https://data.sisense.com/linux/*

Thanks for your support.

[Cleber]

Also, looking at this like: https://docs.sisense.com/main/SisenseLinux/upgrading-from-kubespray-to-rke.htm

It's recommended steps to migrate the Kubespray to RKE.

But the version on the top left corner says L2023.3.0; it's the right document/step to proceed with migration from L2022.10.0?

[Anonymous]

Hello @Cleber,

Migration to RKE doesn't apply to the deployments in EKS/AKS/GKE. That is why when you upgraded from L2022.6 to L2022.11, the Sisense deployment scripts skipped the RKE steps. Both Kubespray and RKE are used to deploy Kubernetes clusters. Since you are installing only Sisense on a preexisting cluster i.e. EKS the installer would only install Sisense components into your existing cluster. 

In summary, anyone using cloud_config.yaml does not need to perform Kubespray to RKE migration steps as they are not using Kubespray or RKE, but their own cloud-provided cluster.

As for the kubespray directory, it is just a legacy directory/subdirectory name.

I hope this answers your question.

Best Regards.