System Requirements

The Palette SaaS platform is also available as a self-hosted, on-premises deployment. The on-premises version is a dedicated instance of the platform hosted in the customer's VMware environment. Palette on-premises is available in two modes:

On-premises ModesDescription
Enterprise ModeA multi-node, highly available version for production purposes.
Quick Start ModeA single VM deployment of the platform ideal for proof-of-concept (PoC) purposes.

The sections below describe the standard requirements and highlight specific requirements for both deployment modes.

vSphere Environment Prerequisites

General requirements

  • vCenter version : 6.7 and above
  • NTP configured on all ESXi Hosts

Zone Tagging

Zone tagging is required for dynamic storage allocation across fault domains when provisioning workloads that require persistent storage. This is required for the installation of the Palette platform itself and is also useful for Workloads deployed in the Tenant Clusters, if they have persistent storage needs. Use vSphere tags on data centers (kubernates-region) and compute clusters (kubernetes-zone) to create distinct zones in your environment.

As an example, assume your vCenter environment includes three compute clusters: cluster-1, cluster-2, and cluster-3 as part of data center dc-1. You can tag them as follows:

vSphere ObjectTag CategoryTag Value

Note: The exact values for the kubernates-region and kubernates-zone tags can be different from the ones described in the example above, as long as they are unique.


The following permissions are required for the account used to install the platform:

vSphere Object

Datastore Privileges

  • Allocate Space
  • Browse Datastore
  • Low level file operations
  • Remove file
  • Update virtual machine files
  • Update virtual machine metadata

Network Requirements

  • Outgoing access from the platform VMs to the internet either directly or via a proxy.
  • An IP Address (static or DHCP) for the quick start virtual machine (also used as an installer for enterprise version).
  • A block of five (5) IP addresses reserved for an enterprise cluster: One IP address for each of the three enterprise cluster VMs, an IP to be used as a VIP, and an additional IP reserved for rolling upgrades.
  • Interconnectivity across all the three (3) VMs on all ports.
  • Connectivity from the Virtual Machines to the vCenter.
Make sure that your Data center CIDR IP address does not overlap Kubernetes PodCIDR range. Kubernetes PodCIDR range settings can be changed during installation.

Proxy Requirements

  • If a proxy is used for outgoing connections, it should support both HTTP and HTTPS traffic.
  • Connectivity to the following domains and ports should be allowed:

    Top-level DomainPortDescription
    spectrocloud.com443Spectro Cloud content repository and pack registry
    s3.amazonaws.com443Spectro Cloud VMware OVA files
    gcr.io443Spectro Cloud and common 3rd party container images
    docker.io443Common 3rd party container images
    googleapis.com443For pulling Spectro Cloud images
    docker.com443Common 3rd party container images
    raw.githubusercontent.com443Common 3rd party content
    projectcalico.org443Calico container images
    quay.io443Common 3rd party container images
    grafana.com443Grafana container images and manifests
    github.com443Common 3rd party content

Hardware Requirements

The following section provides the hardware requirements for Palette Platform VMs for various capacity levels.

Capacity LevelsDescription
Concurrent Tenant ClustersThe number of concurrent tenant cluster provisioning or deletion requests.
Total Managed ClustersThe number of parallel running tenant clusters.

The size of the Tenant Cluster, in terms of the number of nodes or size of the nodes, does not impact the capacity guidance below.

On-premises Configurations

Configuration NameConcurrent
Max NodesCPUsMemoryStorageMongoDB LimitRunning Workload
Small4100048 GB60 GB20 GB, 1 CPU, 2 GB MemUp to 1000 Nodes each with 30 Pods (30,000 pods)
Medium(Default)83000816 GB120 GB60 GB, 2 CPU, 4 GB MemUp to 3000 Nodes each with 30 Pods (90,000 pods)
Large1250001232 GB150 GB80 GB, 2 CPU, 6 GB MemUp to 5000 Nodes each with 30 Pods (150,000 pods)

Quick Start and Enterprise Configurations

Quick StartSmall42018 GB4 Virtual CPUs80 GB
EnterpriseMedium8500* (Cluster having 6 nodes
and each node with 30 pods)
316 GB8 Virtual CPUs120 GB

For high availability purposes, it is recommended that you deploy the three (3) VMs across three (3) compute clusters.

Best Practices

The following steps are optional but recommended for production environments.

DNS MappingA DNS is used to access the Palette Management Console. While the Virtual IP Address (VIP) configured on the platform can be used
to access the platform, it is recommended that you reserve a DNS for this purpose and map it to the VIP after installation.
SMTP SettingsConfigure the SMTP settings to enable the Palette platform to send out email notifications. Email notifications are sent out to new
users, when they are initially onboarded onto the platform, so they can activate their accounts and reset their password at a later time.
Trusted CertificateConfigure your platform with a trusted CA certificates.
FTP Location for backupsConfigure an FTP location for platform backups and schedule daily backups.