KubeOps
Infra Onboarding
Admin
BP’s Guided Cluster Onboarding #
BuildPiper facilitates the seamless onboarding of existing Kubernetes clusters — EKS, GKE, AKS, or on-premises — allowing teams to manage and deploy workloads directly from the platform, backed by a unified Cluster Health Dashboard for day-to-day operational visibility.
BuildPiper supports onboarding Kubernetes clusters hosted on major cloud providers as well as private infrastructure. You can connect clusters running on the following platforms:
AWS, including managed Kubernetes services such as Amazon EKS.
Azure Kubernetes Service (AKS) for managed Kubernetes on Microsoft Azure.
Google Kubernetes Engine (GKE), Google Cloud’s managed Kubernetes offering.
On-Premises / Private Infrastructure
Clusters running on on-premises or private infrastructure (LDC).
Oracle Cloud Infrastructure
Kubernetes clusters provisioned and hosted on Oracle Cloud Infrastructure.
Kubernetes clusters running on Alibaba Cloud’s container service.
Kubernetes clusters hosted on the IBM Cloud Kubernetes Service.
Linode Kubernetes Engine, now part of Akamai Technologies.
Kubernetes clusters provisioned on Huawei Cloud’s container engine.
Supported Cloud & Private Infrastructure Providers
These integrations allow you to register your existing Kubernetes clusters with BuildPiper and manage deployments directly from the platform.
Cluster onboarding is completed from the BuildPiper console in three steps — Login to BP → Add Cluster → Add cluster details and upload .kubeconfig.
Step 1 — Log in to BuildPiper
Sign in to the BuildPiper platform using an account that has administrator privileges.
Navigate to the cluster section and select Add Cluster to begin onboarding.
Step 3 — Add Details & Upload Kubeconfig
Enter the cluster details and upload the .kubeconfig file to complete registration.
📌 Note — Before You Begin
• Admin privileges are required to access this functionality.
• The onboarding team must have the Kubernetes cluster Kubeconfig file.
• BuildPiper supports Kubernetes versions from 1.26 up to the latest 1.32.
The screenshots below are provided for reference across the cluster onboarding flow.
BP Snapshot — Cluster Onboarding
BP Snapshot — Processing / Validating the .kubeconfig File
BP Snapshot — Accessing the Cluster Once Onboarded
After a cluster is successfully onboarded to the BuildPiper platform, users can access the Cluster Health Dashboard — showing control plane component status, Kubernetes version, real-time CPU and memory utilization, worker node health summary, and total namespaces. This provides a quick operational view of cluster stability and resource usage. The visible components are:
A granular status indicator for essential cluster components — including etcd, CoreDNS, and the Controller Manager — verifying the operational integrity of the cluster’s core planes.
Displays the control plane version (for example, v1.28.x) as reported by the Kubernetes API server.
K8s Cluster Resource Utilization Metrics
Real-time graphs displaying aggregate CPU and Memory (RAM) consumption across the entire cluster, calculated as a percentage of total allocatable resources.
A summarized view of the node pool, detailing the count of worker nodes and their operational state (Healthy / Unhealthy).
A total count of the namespaces present in the cluster, reflecting the logical segmentation of the environment.
📘 BuildPiper Documentation · Cluster Onboarding
Last updated: May 2026
