Fuzzball Documentation
Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage

Requirements

For information about setting up a basic RKE2 cluster and the dependencies necessary to install Fuzzball, please see the RKE2 cluster installation guide in the appendices.

This guide was developed on Rocky v8.10 instances running within the Vultr cloud platform, sharing a virtual network.

Hardware

  • The Server node should have at least 6 cores and 16 GBs of memory.
  • The Compute nodes will comprise the actual cluster that runs user workflows. The hardware requirements will therefore be determined by the expected workflows.
  • The nodes are assumed to share an internal network.

Access to CIQ Depot

This guide assumes access to CIQ Depot. Depot provides a secure delivery platform for a number of asset types, including RPM packages and SIF/OCI container images. It will be used to obtain the Fuzzball operator and the Fuzzball image that the operator will deploy.

NFS

Fuzzball Orchestrate uses NFS distribute configuration to compute nodes and exchange containers.

Kubernetes and Some Associated Tooling

This guide was developed using RKE2. Other K8s flavors should also work but are untested at this time.

metallb

A bare-metal deployment RKE2 requires the metallb load-balancer for the assignment of external IP addresses.

Helm

Helm is used to deploy the Fuzzball Operator.

Local Path Provisioner or another StorageClass

The Fuzzball Operator requires the use of a StorageClass to preserve state. It can simplify the procedure to set the StorageClass as default. These guides assume Local Path Provisioner is in use.

If you need to install a basic set of these dependencies on a fresh machine, head to the RKE2 cluster installation guide in the appendices. If you already have these dependencies installed, you can feel free to advance to the next step in the deployment guide.