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:
|Enterprise Mode||A multi-node, highly available version for production purposes.|
|Quick Start Mode||A 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.
- vCenter version : 6.7 and above
- NTP configured on all ESXi Hosts
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 Object||Tag Category||Tag 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:
- Allocate Space
- Browse Datastore
- Low level file operations
- Remove file
- Update virtual machine files
- Update virtual machine metadata
- 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.
- 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 Domain Port Description spectrocloud.com 443 Spectro Cloud content repository and pack registry s3.amazonaws.com 443 Spectro Cloud VMware OVA files gcr.io 443 Spectro Cloud and common 3rd party container images docker.io 443 Common 3rd party container images googleapis.com 443 For pulling Spectro Cloud images docker.com 443 Common 3rd party container images raw.githubusercontent.com 443 Common 3rd party content projectcalico.org 443 Calico container images quay.io 443 Common 3rd party container images grafana.com 443 Grafana container images and manifests github.com 443 Common 3rd party content
The following section provides the hardware requirements for Palette Platform VMs for various capacity levels.
|Concurrent Tenant Clusters||The number of concurrent tenant cluster provisioning or deletion requests.|
|Total Managed Clusters||The number of parallel running tenant clusters.|
|Configuration Name||Concurrent |
|Max Nodes||CPUs||Memory||Storage||MongoDB Limit||Running Workload|
|Small||4||1000||4||8 GB||60 GB||20 GB, 1 CPU, 2 GB Mem||Up to 1000 Nodes each with 30 Pods (30,000 pods)|
|Medium(Default)||8||3000||8||16 GB||120 GB||60 GB, 2 CPU, 4 GB Mem||Up to 3000 Nodes each with 30 Pods (90,000 pods)|
|Large||12||5000||12||32 GB||150 GB||80 GB, 2 CPU, 6 GB Mem||Up to 5000 Nodes each with 30 Pods (150,000 pods)|
|Quick Start||Small||4||20||1||8 GB||4 Virtual CPUs||80 GB|
|Enterprise||Medium||8||500* (Cluster having 6 nodes |
and each node with 30 pods)
|3||16 GB||8 Virtual CPUs||120 GB|
The following steps are optional but recommended for production environments.
|DNS Mapping||A 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 Settings||Configure 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 Certificate||Configure your platform with a trusted CA certificates.|
|FTP Location for backups||Configure an FTP location for platform backups and schedule daily backups.|