Architecture
This is a Tech Preview feature and is subject to change. Do not use this feature in production workloads. This feature is supported in self-hosted Palette only.
Palette supports using Apache CloudStack as a data center provider. You can deploy Kubernetes clusters to your CloudStack environment using Palette. The CloudStack management environment could include Bare Metal (via IPMI), Hyper-V, Kernel-based Virtual Machine(KVM), Linux Containers (LXC), vSphere (via vCenter), Xenserver and Xen Project. Below are some key features of the Palette CloudStack architecture:
-
Support for static IP addresses, as well as DHCP. If you are using Dynamic Host Configuration Protocol (DHCP), Dynamic DNS is required.
-
Support for IP address pool management for assigning blocks of IPs dedicated to clusters or projects.
-
A Private Cloud Gateway (PCG) must be setup within the CloudStack environment to communicate with the Palette management platform and the Apache CloudStack management platform that installed in the private data center.
The PCG facilitates communication between Palette and your infrastructure environment. The PCG is necessary in environments where Palette does not have direct network access. Many infrastructure environments are placed in a private network that blocks connections originating externally. The PCG connects to Palette, and acts as an endpoint, allowing you to target the environment when deploying clusters in Palette.
-
Support for Projects within a Domain. You can use Apache CloudStack projects to separate workload resources among different teams, as CloudStack tracks resource usage per project and per user.
You can learn more in the PCG Architecture section.