3 min read

Kaphera Cloud Terraform Provider

A Terraform provider that exposes every CRD and server endpoint as declarative resources and data sources, with the same three backends as the CLI: kubernetes, server, and cloud.

What it is

A Terraform provider that exposes the same three backends as the [[kaphera-cli|kaphera CLI]] (kubernetes, server, and cloud) as declarative Terraform resources and data sources. Written in Go using the Terraform Plugin Framework. Currently 22 resources and 14 data sources covering every CRD and server endpoint. Lets teams manage EDC infrastructure alongside their existing Terraform-managed cloud resources with terraform plan and terraform apply.

What it does for the customer

Makes EDC infrastructure management declarative and auditable through Terraform’s plan/apply workflow. A platform team defines their EDC deployment (databases, vaults, connectors, data space profiles) in the same Terraform configuration that manages their VPC, DNS, and monitoring. Changes go through the same review and approval process as all other infrastructure. For systems integrators, it enables templated, repeatable deployments: define a connector setup once, parameterise it, and apply it to every client.

Who it serves

lars-hoffmann is the builder who manages infrastructure as code. The kubernetes backend lets him manage kaphera-edc-operator and kaphera-edc-enablement-operator resources through Terraform with no server dependency, directly into his existing ArgoCD and GitOps workflow.

marco-ferretti’s engineering team uses the provider to automate repeatable client deployments as part of their white-label service.

dirk-wassermann’s platform engineers manage the BYOC deployment through the same Terraform configuration that manages their private cloud infrastructure.

Why this licence: Apache 2.0

Same rationale as the [[kaphera-cli|kaphera CLI]]. The provider is an enablement tool that drives adoption of the operators and platform. Restricting it would force teams to choose between Kaphera and their existing IaC workflow. Revenue comes from what the provider manages, not from the provider itself.

How it relates to other artefacts

Companion to the [[kaphera-cli|kaphera CLI]]: shared backend abstraction, same context configuration, same three modes. The kaphera-cloud-terraform-modules are the opinionated layer on top of this provider; they compose provider resources into production-ready patterns. For the kubernetes backend, it talks directly to CRDs managed by the kaphera-edc-operator and kaphera-edc-enablement-operator. For server and cloud backends, it talks to the kaphera-cloud-server and kaphera-cloud-managed-server respectively.

Graph View

Backlinks