Skip to main content
Version: latest


Palette VerteX is available as a self-hosted application that you install in your environment. The self-hosted version is a dedicated Palette VerteX environment hosted on VMware instances or in an existing Kubernetes cluster. Palette VerteX is available in the following modes:

Supported PlatformDescriptionInstall Guide
VMwareInstall Palette VerteX in VMware environment.Install on VMware
KubernetesInstall Palette VerteX using a Helm Chart in an existing Kubernetes cluster.Install on Kubernetes

You can also install Palette VerteX in an airgap environment. For more information, refer to the Airgap Installation section.

Supported Airgap PlatformDescription
VMwareInstall Palette VerteX in VMware environment using your own OCI registry server.
KubernetesInstall Palette VerteX using a Helm Chart in an existing Kubernetes cluster with your own OCI registry server OR use AWS ECR.

The next sections describe specific requirements for installing Palette VerteX.

Size Guidelines

This section lists resource requirements for Palette VerteX for various capacity levels. In Palette VerteX, the terms small, medium, and large are used to describe the instance size of worker pools that Palette VerteX is installed on. The following table lists the resource requirements for each size.


The recommended maximum number of deployed nodes and clusters in the environment should not be exceeded. We have tested the performance of Palette VerteX with the recommended maximum number of deployed nodes and clusters. Exceeding these limits can negatively impact performance and result in instability. The active workload limit refers to the maximum number of active nodes and pods at any given time.

SizeNodesCPUMemoryStorageMongoDB Storage LimitMongoDB Memory LimitMongoDB CPU LimitTotal Deployed NodesDeployed Clusters with 10 Nodes
Small3816 GB60 GB20 GB4 GB21000100
Medium (Recommended)31632 GB100 GB60 GB8 GB43000300
Large33264 GB120 GB80 GB12 GB65000500

Instance Sizing

ConfigurationActive Workload Limit
SmallUp to 1000 Nodes each with 30 Pods (30,000 Pods)
Medium (Recommended)Up to 3000 Nodes each with 30 Pods (90,000 Pods)
LargeUp to 5000 Nodes each with 30 Pods (150,000 Pods)

Proxy Requirements

  • A proxy used for outgoing connections should support both HTTP and HTTPS traffic.

  • Allow connectivity to domains and ports in the table.

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