The network ports for Palette in SaaS mode and on-prem are listed below.
| Port | Direction | Purpose |
|---|---|---|
| HTTPS (tcp/443) | IN | Browser/API access to Management Platform |
| SSH (tcp/22) | IN | Troubleshooting via SSH (optional) |
| NATS (tcp/4222) | IN | Agent running inside connecting to Management Platform |
| Port | Direction | Purpose |
|---|---|---|
| HTTPS (tcp/6443) | IN | Kubernetes API Server |
| SSH (tcp/22) | IN | Troubleshooting via SSH (optional) |
| NATS (tcp/4222) | OUT | Registry (packs, integrations), Pack containers, Application Updates |
The following diagram maps the network connections between the Palette components and deployed Kubernetes clusters.
| Port | Direction | Purpose |
|---|---|---|
| HTTPS (tcp/443) | IN | Browser/API access to Management Platform |
| SSH (tcp/22) | IN | Troubleshooting via SSH (optional) |
| NATS (tcp/4222) | IN | Message Bus for workload clusters |
| HTTPS (tcp/443) | OUT | vSphere vCenter API, Registry (packs, integrations), Pack containers, app updates. |
| HTTPS (tcp/6443) | OUT | Workload K8s cluster API Server |
| Port | Direction | Purpose |
|---|---|---|
| HTTPS (tcp/6443) | IN | Kubernetes API Server |
| SSH (tcp/22) | IN | Troubleshooting via SSH (optional) |
| NATS (tcp/4222) | OUT | Agent communication via Message Bus |
| HTTPS (tcp/443) | OUT | vSphere vCenter API, Registry (packs, integrations), Pack containers, Application updates. |