Overview

A Fleet Plan on clusters refers to a strategic approach for managing and coordinating resources across multiple clusters. It involves creating a comprehensive plan to streamline operations on a bunch of clusters available within one or more fleet(s), and ensure efficient utilization of cluster resources. With Fleet Plan, users can effortlessly perform a wide range of operations such as upgrades, backups, patching, and scaling across their clusters. The base roles Infra admin and Org Admin are allowed to create and run the fleet plan.

Benefits

Users Benefit from Fleet Plan in the following Ways:

• Cluster Management: Oversee and control multiple clusters simultaneously
• Upgrade: Simplifies the process of upgrading clusters within the fleet
• Backups: Conveniently manage and schedule backups for their clusters
• Patching: Streamlines the patch management process for clusters within the fleet
• Scaling: Easily scale their clusters up or down to accommodate changing workload demands

Did you know?

An Org Admin/ Infra Admin can create Cluster Fleet Plans via three methods:

• UI
• CLI
• Swagger API

Supported Cluster Types

Fleet Plan is supported for the following cluster types:

• Amazon EKS
• Azure AKS
• Google GKE

Note

Fleet Plans are cluster-type specific. EKS, AKS, and GKE clusters cannot be combined into the same Fleet Plan. A separate Fleet Plan must be created for each cluster type.

Pre-requisites

• Fleet plan refers to labels to target the clusters
• GitOps agent is required for executing the hooks in fleet plan when Runner type is configured as Agent in the hook configuration
• Container image is necessary for hooks (pre and post hook configuration)

UI Process Flow Diagram

The image below describes the typical steps that are performed in a sequence.

"Trigger the job" "Add Agents" "Select Labels & Projects" "Add Pre/Post-hook Config" "New Operations" "Create Fleet Plan" User "Trigger the job" "Add Agents" "Select Labels & Projects" "Add Pre/Post-hook Config" "New Operations" "Create Fleet Plan" User Login as Org Admin/Infra Admin Optional Mandatory when Runner type is Agent in Hook config Add one or more Operations​ Pre/Post-hook checks for the operations Select one or more projects Add one or more GitOps CD Agents Apply the operations on the targets (clusters)