Skip to main content
Version: latest

Architecture

Canonical MAAS is an open source tool that lets you discover, commission, deploy and re-deploy operating systems to physical servers. The following are some architectural highlights of bare-metal Kubernetes clusters that Palette deploys using Canonical MAAS. Refer to the PCG deployment options section below to learn more about PCG deployment.

  • Palette integrates with MAAS through Spectro Cloud’s open source Cloud Native Computing Foundation (CNCF) Cluster API provider. Refer to the table below.

  • Palette provides a cloud-like experience for deploying clusters on MAAS-managed bare-metal servers or on LXD virtual machines created by MAAS. Bare metal typically provides near-native performance, while LXD VMs improve consolidation and resource utilization with minimal additional overhead.

Network flow from an architectural perspective of how MAAS LXD works with Palette

  • A Private Cloud Gateway (PCG) that you install in a MAAS cloud using a local installer facilitates communication between Palette and MAAS. The PCG is necessary in MAAS environments where Palette does not have direct network access to the MAAS server. Since MAAS environments are typically in a private network without a central endpoint, the PCG provides this endpoint and also wraps the MAAS environment into a cloud account that you can target for cluster deployment in Palette. Refer to the section below to learn about the PCG deployment options you have.

  • Support for static IP addresses is available through IP Pools provisioned in the PCG.

  • Dynamic Host Configuration Protocol (DHCP) is also supported. If you are using DHCP, dynamic DNS is required.

  • When the PCG is installed, it registers itself with a Palette instance and enables secure communication between the SaaS portal and the private cloud environment. The gateway enables installation and end-to-end lifecycle management of Kubernetes clusters in private cloud environments from Palette's SaaS portal.

    The diagram below illustrates how MAAS works with Palette using a PCG.

    Network flow from an architectural perspective of how MAAS works with Palette

Refer to the PCG Architecture section to learn more about the PCG architecture.

Limitations

The Canonical Kubernetes pack for deployments in MAAS environments is a Tech Preview feature and does not support cluster backups with volume snapshots.

Palette MAAS Distribution

Palette provides the following distributions for MAAS environments.

NameKubernetes DistributionOSCNIsCSIs
Palette eXtended Kubernetes (PXK)CNCFUbuntu, BYOOSMultiple. Refer to the pack information for the details.Multiple. Refer to the pack information for the details.
Canonical KubernetesCanonical KubernetesUbuntu for Canonical KubernetesCilium CNI (Canonical Kubernetes)Portworx
tech preview

The Canonical Kubernetes pack for deployments in MAAS environments is a Tech Preview feature and is subject to change. Do not use this feature in production workloads.

Custom API Server Endpoint for MAAS Clusters

By default, Palette registers a DNS record in MAAS for the deployed cluster and links it to the IP addresses of the control plane nodes of the cluster. However, you may choose not to depend on MAAS for your cluster DNS record. The Kubernetes pack allows you to configure a custom API server endpoint for your cluster instead.

This feature is only supported in Palette eXtended Kubernetes (PXK). Refer to the Custom API Server Endpoint for MAAS Clusters section of the pack Additional Guidance for further information.