Edka Developer Documentation
What is Edka?
Edka automates the creation of a production ready Platform as a Service (PaaS) on top of standard cloud virtual machines and Kubernetes. It reduces the manual effort required to run applications on Kubernetes by providing pre-configured open source add-ons and applications that transform a Kubernetes cluster into a full-fledged PaaS.
Edka provisions and manages Kubernetes clusters in your own Hetzner Cloud account. If you disconnect Edka, you retain full control and can continue managing your clusters with tools like kubectl, Lens or GitOps.
How It Works
- Cluster Bootstrap
Provision a Kubernetes cluster on Hetzner Cloud and configure the control plane through a simple UI.
- Add‑ons installation
Install a curated set of production add‑ons like ingress controllers, certificate management, metrics, and operators preconfigured for Hetzner Cloud. No manual setup required.
- Applications
Deploy applications that can be customized with a few parameters before launch. Configure them via a minimal UI. Edka handles sane defaults and Hetzner specific configurations. For example, deploy PostgreSQL with a single click and optionally configure:
- Number of instances
- Storage allocation
- Continuous backups to S3 or GCS
- Point‑in‑time recovery
- Connect a Container Registry
Connect a private or public container registry (e.g., GHCR, Docker Hub, GitLab) to enable automatic image pulls for your workloads.
- Deployments
Deploy any container image from the Edka dashboard. Configure:
- Replica count
- CPU and memory limits/requests
- Persistent volumes
- Environment variables and secrets
- Automatic updates via SemVer policies
- Horizontal auto‑scaling
- Instant public exposure with built‑in TLS termination
- Sync Your Secrets (Optional)
Integrate external secrets managers such as 1Password, Doppler, HashiCorp Vault, AWS Secrets Manager, and more. Secrets are synced directly to your clusters; Edka never stores them. We recommend Doppler for simplicity.
- GitOps (Optional)
Connect a Git repository to enable continuous reconciliation (GitOps). When you push manifests or Helm charts, they are applied automatically to the cluster. For disaster recovery, connect a new cluster to the same repository to restore state.