Platform Operator

Klutch provides a centralized control plane for managing Data Services across multiple Kubernetes clusters. It gives Platform Operators a unified, Kubernetes-native interface to orchestrate, govern, and enable the full lifecycle management of all Data Services across the entire fleet of App Clusters.

The Platform Operator Workflow

Klutch provides a consistent operational model for managing Data Services across environments. Depending on organizational requirements and supported automation backends, platform operations typically follow this pattern:

1. Setup the Control Plane: Deploy the Klutch Control Plane as the central coordination layer. This establishes the API, orchestration components, and integrations required to manage Data Services.
2. Configure Data Service Offerings: Connect automation backends and define Service Plans to make a selected set of supported Data Services available for binding from App Clusters. See Creating a Custom Crossplane Package for more on defining custom Service Plans.
3. Connect App Clusters: App Clusters are bound to the Control Plane so that the Klutch API becomes available within each cluster and service requests can be submitted using Kubernetes Custom Resources.
4. Operate and Govern the Platform: Day-2 activities include monitoring service health and usage, managing plans, and performing lifecycle, security, and compliance-related operations across connected clusters.

For concrete setup instructions and configuration examples, refer to the dedicated Platform Operator pages in this section.