Requirements
You need a few things before you begin deploying your new Federate instance.
The Federate deployment method leverages the K8s infrastructure of an existing Fuzzball Orchestrate cluster. This is appropriate because the purpose of Federate is to manage Orchestrate clusters. If you have not already done so, consult the Local Admin Guides or Cloud Admin Guides to learn how to deploy a Fuzzball cluster in the environment of your choice.
You can deploy Federate and use it to manage a single Orchestrate cluster. But the real value of Federate emerges when you have 2 or more existing Fuzzball Orchestrate clusters to manage. Therefore, we recommend installing and using Federate when you have 2 or more clusters that you want to manage together.
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 Federate images that will be deployed.
You should have the kubectl
command installed either locally (if your local environment is configured with the context pointing
to your Fuzzball deployment) or on the node where you set up K8s and are running Fuzzball. You
should already have this requirement satisfied since you used it to deploy your Fuzzball cluster.
You should have the AWS CLI installed locally and configured to access your account. If you already deployed your a Fuzzball cluster in AWS via the marketplace listing, you should already have this requirement satisfied.
If you are deploying Federate alongside your existing Orchestrate cluster on-prem you will need a slightly larger machine to accommodate all of the running pods.