Skip to content
Sosivio

Prerequisites

Supported Environments

Sosivio is fully supported for the following Kubernetes environments:

  • Kubernetes ("on-prem") v1.16 and above
    • This includes IaaS for cloud providers (EC2, Compute Engine, VMs, etc.)
  • Openshift 4.x
  • Amazon Web Services - Elastic Kubernetes Service v1.16 and above
  • Google Cloud Platform - Google Kubernetes Engine v1.16 and above
  • Microsoft Azure - Azure Kubernetes Service v1.16 and above

Dependencies

On Premise Deployment - Disconnected

When installing Sosivio on-premise in a disconnected environment, Sosivio container images must be downloaded and pushed to a local repository. See the installation instructions for disconnected environments here for more details.

Amazon Web Services - Elastic Kubernetes Service (EKS) Deployment

When installing Sosivo on EKS a service type LoadBalancer in your EKS cluster is automatically created and an AWS Network Load Balancer (NLB) is provisioned, which load balances network traffic.

The Sosivio Installer automatically pulls the address for the NLB. There is no action required by users.

NOTE: By default, the LoadBalancer service creates a Classic Load Balancer.

Microsoft Azure - Azure Kubernetes Service (AKS) Deployment

The HTTP application routing solution makes it easy to access applications that are deployed to your Azure Kubernetes Service (AKS) cluster. When the solution is enabled, it configures an ingress controller in your AKS cluster. As applications are deployed, the solution also creates publicly accessible DNS names for application endpoints. When the add-on is enabled, it creates a DNS Zone in your subscription.

You will be required to follow one of the two options for enabling HTTP routing below. You can enable this option via the CLI or Azure web portal.


Deploy HTTP Routing: CLI

The HTTP application routing add-on can be enabled with the Azure CLI when deploying an AKS cluster. To do so, use the az aks create command with the --enable-addons argument:

az aks create --resource-group myResourceGroup --name myAKSCluster --enable-addons http_application_routing


Deploy HTTP Routing: Azure Portal

During the installation of your AKS cluster, ensure you enable the Application Gateway ingress controller under the Networking section.

Application Gateway ingress controller

After the cluster is deployed, navigate to the auto-created AKS resource group and select the Properties tab. The HTTP application routing domain name will be the name used during the installation when asked for the URL of your ingress controller.

HTTP Application Routing Domain Name

Google Cloud Platform - Google Kubernetes Engine (GKE) Deployment

When installing Sosivo on GKE, the Sosivio Dashboard needs to be exposed in order to communicate with your browser. During the installation process a service type LoadBalancer in your GKE cluster and Google Cloud controller Network Load Balancer (NLB) are automatically created.

The Sosivio Installer automatically pulls the address for the NLB. There is no action required by users.

Other Managed Kubernetes Services/Customized environments

If you are using any other configurations in EKS, AKS, GKE or another Managed Kubernetes Service, please contact us for support at [email protected].

Performance Requirements

Disconnected Environments

When installing on Kubernetes, you will need:

  • Cluster-admin privileges
  • Minimum of 3 Nodes
  • Minimum available resources per node required are:
    • 4 CPU/vCPU
    • 8 GB RAM

Requirements are for the first 3 Nodes and only for the installation. Sosivio's actual resource consumption is always less than 5% of the total cluster resources.

Connected Environments

When installing on Kubernetes, you will need:

  • Cluster-admin privileges
  • Minimum of 3 Nodes
  • Minimum available resources per node required are:
    • 4 CPU/vCPU
    • 8 GB RAM

CPU Architecture

Sosivio runs only on x86_64 processor architectures.