Skip to main content
Version: 0.4

Konstruct 0.4

Released: March 2026

Highlights​

  • Hosted Control Plane — Civo now offers a fully managed Konstruct control plane at konstruct.saas.civo.com
  • Civo Cloud Support — provision management and workload clusters on Civo from both hosted and self-hosted installs
  • Multi-Cloud Workload Clusters — run workload clusters on AWS and GCP alongside Civo from a single management cluster
  • Simplified Hosted Onboarding — go from sign-up to a running management cluster without installing anything

Hosted Control Plane​

Konstruct 0.4 introduces the Hosted Control Plane, a SaaS offering where Civo manages the control plane tier. Platform teams get the full Konstruct experience — GitOps workflows, cluster provisioning, application delivery — without provisioning or maintaining the control plane infrastructure themselves.

2-Tier Experience for Hosted Users​

With the hosted model, the control plane tier is abstracted away. Users interact with a two-tier architecture:

  1. Your Management Cluster (Civo Kubernetes) — hosts ArgoCD, Crossplane, and your platform tooling
  2. Your Workload Clusters (Civo, AWS, or GCP) — run your applications

The Konstruct operators, API, and UI run on Civo-managed infrastructure. Civo handles availability, upgrades, and security patching.

Getting Started with Hosted​

  1. Sign up at konstruct.saas.civo.com using your Civo account
  2. Create an organization
  3. Connect a Civo API key
  4. Provision your first management cluster

See the Hosted Quickstart for a step-by-step walkthrough.

What Hosted Users Own​

The hosted control plane does not reduce your ownership of the platform tier:

  • You own and operate your management cluster
  • You own the GitOps repository backing your platform
  • You own and operate all workload clusters
  • You can customize platform tooling via your GitOps repo

See Hosted Control Plane for architecture details and Limitations for current constraints.

Civo Cloud Support​

Management clusters can now be provisioned directly on Civo Kubernetes from Konstruct. Connect a Civo API key as a cloud account and select Civo when creating a management or workload cluster.

This is the required cloud provider for management clusters in the hosted model. Self-hosted users can also provision management and workload clusters on Civo.

Multi-Cloud Workload Clusters​

A single management cluster can now provision and manage workload clusters across multiple cloud providers simultaneously. In 0.4, the supported workload cluster clouds from a single management cluster are:

  • Civo
  • AWS (EKS)
  • GCP (GKE)

Each workload cluster uses its own cloud account credential, scoped to that cluster's provisioning and secrets access.

Simplified Hosted Onboarding​

The Konstruct UI at konstruct.saas.civo.com includes a guided setup flow for new organizations:

  1. Connect a Civo cloud account
  2. Connect a Git account (GitHub or GitLab)
  3. Create a management cluster
  4. Create your first workload cluster

No Helm install or cluster prerequisites are required.

Breaking Changes​

None in 0.4. Self-hosted installs continue to work without changes. The 0.4 umbrella chart is backward-compatible with 0.3.x configurations.

Upgrading Self-Hosted​

Standard Helm upgrade:

helm upgrade konstruct oci://europe-west2-docker.pkg.dev/civo-com/charts/konstruct \
  --version 0.4.0 \
  --namespace konstruct-system \
  --reuse-values

Update targetRevision in your ArgoCD Application manifest if you manage the install via GitOps:

spec:
  source:
    chart: konstruct
    repoURL: oci://europe-west2-docker.pkg.dev/civo-com/charts
    targetRevision: 0.4.0
    helm:
      values: |
        global:
          konstructVersion: "v0.4.0"

What's Next?​