This page describes the software, hardware, and networking requirements for the nodes where Shipa will be installed.
This document applies only to Self-Managed Shipa. If, instead, you prefer Shipa Cloud, please visit https://apps.shipa.cloud and register. From there on, you can add existing Kubernetes cluster to be managed by Shipa Cloud by following the instructions in Connecting Clusters.
Today, Shipa supports Kubernetes clusters versions 1.16 and higher.
Tested and supported clusters are:
- On-premises clusters
- GKE (Google Kubernetes Engine)
- AKS (Azure Kubernetes Service)
- EKS (Amazon Elastic Kubernetes Service)
- OKE (Oracle Kubernetes Engine)
- LKE (Linode Kubernetes Engine)
Only single-zone clusters are supported on Shipa's free version.
Shipa currently supports only 64-bit x86 Linux nodes.
It is tested with ContainerD and Docker as container runtime. However, it should work in any runtime that implements Container Runtime Interface (CRI).
Hardware requirements scale based on the size of your deployment that is controlled by Shipa. These resource consumptions are at the node level, nodes where Shipa will be installed.
|Size 1||Up to 200||2||8 GB|
|Size 2||Up to 500||4||16 GB|
|Size 3||Up to 1000||8||32 GB|
|Size 4||1000+||Contact our team||Contact our team|
During the install, Shipa creates and uses two public IPs for Load Balancers. These Load Balancer services expose some of the Shipa services, using the following ports:
|8080||Shipa API over HTTP|
|8081||Shipa API over HTTPS|
By default, during the install, Shipa uses dynamic public IP set by the cloud provider. If preferred, static IP can be used instead by applying the optional parameter below when using Helm install:
--set service.nginx.loadBalancerIP=<Static IP>
Updated about a month ago