Skip to content
SYS.DOCS // DOCS

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

  1. Cluster Bootstrap

    Provision a Kubernetes cluster on Hetzner Cloud and configure the control plane through a simple UI.

  2. 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.

  3. 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
  4. 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.

  5. Deployments

    Deploy any container image from the Edka dashboard. Configure:

    • Replica count
    • CPU and memory limits/requests
    • Persistent volumes
    • Environment variables and secrets
    • Real-time logs
    • Automatic updates via SemVer policies
    • Instant rollback to previous versions
    • Scheduled recurring tasks with Cron Jobs
    • Horizontal auto‑scaling
    • Instant public exposure with built‑in TLS termination

    Deploy from a GitHub repository:

    Same options as container deployments plus:

    • Auto-build on GitHub events
    • Auto-detect programming language and build with Railpack
    • Auto-deploy after successful build
    • Enable preview environments for pull requests
    • Realtime build and deployment status in GitHub
    • Builds and deployments history
  6. Domains and TLS

    Point one or more wildcard subdomains to your cluster’s ingress endpoint.

    Edka will automatically issue and renew TLS certificates for your domains using cert-manager. Certificates are issued and stored in your cluster exclusively. You only delegate DNS to Edka on .acme.edka.net.

    Assign wildcard subdomains for your preview environments.

  7. 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 and user-friendly experience.

  8. 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.