meltcloud

Appearance

Nest ​

Nest is the meltcloud management appliance that hosts the meltcloud API and the Kubernetes Control Planes.

Why use an appliance? ​

When running Kubernetes on bare metal, a problem comes up quickly: modern servers are too powerful to use for just a Control Plane node. Most servers start with at least 256GB of RAM (and can go up to several terabytes), while a Control Plane usually needs only 4–64GB. This makes dedicating a full server to it quite wasteful.

Projects like Kamaji or Hypershift have come up with a smart approach: Hosted Control Planes, where the Kubernetes Control Planes itself are hosted within Kubernetes.

However, this introduces another challenge, the classic Bootstrap Problem: In an empty data center, how to create the first Kubernetes cluster to host the control planes?

A management appliance like Nest addresses both challenges:

  • Solves the bootstrap problem by providing an initial Kubernetes cluster on the appliance
  • Hosts the Control Planes for subsequent clusters

On top of that, it also runs the meltcloud API and Web UI, giving users a central place to deploy and manage their clusters.

Components ​

Nest is made up of the following components:

Nest Components

  • The Foundry, a web process offering a Web UI, the API & background jobs to managed the Kubernetes Control Planes and workers.
  • The Kubernetes Control Planes (consisting of kube-apiserver, etcd and other components) run containerized to use resources efficiently
  • Regular package updates for all involved components (control planes, worker nodes, management appliance) are retrieved via automated release channels.
  • All involved components are remotely monitored by meltcloud.
  • Important data – such as etcds and the Foundry database – are periodically backed up to a user-configured backup location (S3 bucket) for disaster recovery purposes.

Physical vs Virtual Appliance ​

Nest comes as either physical or virtual appliance:

  1. Physical Appliance on meltcloud-provided hardware: We offer preconfigured hardware appliances to be installed on-premises.
  2. Physical Appliance on customer-provided hardware: The customer uses its usual server vendor to spec servers to run Nest. This allows to reuse existing vendor partnerships, processes and monitoring tools.
  3. Virtual Appliance: For trials/PoCs or when virtualized environments are preferred, Nest can also be run as virtual machines.

TIP

Want to try meltcloud without installing Nest in your DC?

Check out our SaaS option where Nest is hosted by us.

Airgapped Scenarios ​

Nest can also run in an airgapped fashion without requiring external connectivity. Be aware that this requires syncing the remote meltcloud packages to your OCI registry and integrating with your own monitoring stack.