Application Developer
Klutch empowers application developers to provision Data Services directly from the App Cluster using standard Kubernetes manifests. Whether consuming a9s VM-based, a8s container-based, or managed cloud services like Amazon S3 and RDS, Klutch provides a unified, self-service workflow that eliminates the need for direct cloud provider access or manual infrastructure tickets.
The Standardized Workflow
Klutch provides a consistent experience across all automation backends. Depending on the Data Service and its capabilities, interactions typically follow this pattern:
- Provision a Data Service Instance: Request a Data Service by applying a Service Instance Custom Resource.
- Bind to a Data Service Instance: Create a Service Binding Custom Resource to generate secure connection credentials and network details.
- Consume a Data Service: The generated Kubernetes Secret is used by the application to access the Data Service.
- Manage a Data Service Instance: Day-2 operations, such as updates, backups, restores, or deletion, are performed by applying, modifying or removing the relevant Custom Resources.
For concrete examples and step-by-step instructions, refer to the dedicated pages for each Data Service in this section.
Scope and Responsibilities
Application developers typically operate exclusively within the App Cluster and interact only with the Klutch APIs exposed there. Responsibilities such as Control Plane configuration, Crossplane® setup, cloud provider integration, and automation backend management are usually handled by a platform operator team.
In this section, you’ll learn how to work with Klutch from an application developer’s point of view. The following pages explain how to provision data services, bind them to applications, and manage their lifecycle using Kubernetes-native patterns.