Skip to content

Integrations

Explore the integrations below to see how you can use kbind with provider-side operators. These retain the original operator setup and example resources, with binding instructions adapted for v2.

Prerequisites

Install the backend, a matching konnector, and the v2 CLI. Examples use provider and consumer kubeconfig contexts and a separate consumer.kubeconfig for CLI apply, substitute your own names and gateway URL.

Run provider setup against provider and consumer manifests against consumer. The guides explicitly switch context before each phase. Wait for the exported consumer CRD to be Established before creating service instances.

v2 preserves namespace, name, and scope. These examples are for disposable, trusted development clusters, not isolated multi-tenant production deployments. Named and label-based related-resource selectors replace the old JSONPath claims, they do not restrict the RBAC granted by provider credentials.

Available Integrations

  • cert-manager: Certificate management as a service.
  • CloudNativePG: Database-as-a-Service on Kubernetes.
  • Crossplane: Example Database-as-a-Service using Crossplane provider.
  • kro: Integrate with kro to serve LoadBalancer-as-a-Service example.