Workload Cluster — Civo
Template Metadata
| Field | Value |
|---|---|
| Repository | konstructio/konstruct-templates |
| Branch / Rev | main |
| Path | cluster-templates/civo/workload-cluster/ |
| Format | Helm chart (civo-workload-cluster v2.0.0) |
| Description | Civo workload cluster with Envoy Gateway and core platform services for application workloads |
Summary
The Civo workload cluster template provisions Civo-based clusters for application workloads. It uses Envoy Gateway instead of NGINX ingress and includes a streamlined set of platform services. Infrastructure provisioning is handled by Crossplane on the parent management cluster, in two phases: the infrastructure Workspace creates the Civo cluster, then infrastructure-bootstrap applies in-cluster bootstrap resources.
The Terraform driving the infrastructure lives in the sibling terraform/civo/modules/workload-cluster and terraform/civo/modules/workload-cluster-bootstrap modules, referenced by URL from the chart's values.yaml.
Sync Wave Deployment Order
| Wave | App Name | Source | Version | Namespace | Description |
|---|---|---|---|---|---|
| 0 | provider-config | gitops repository | HEAD | crossplane-system | Crossplane ProviderConfig for Civo |
| 10 | infrastructure | gitops repository | HEAD | (cluster) | Crossplane infrastructure Workspace |
| 20 | infrastructure-bootstrap | gitops repository | HEAD | (cluster) | In-cluster bootstrap Workspace |
| 30 | cert-manager | charts.jetstack.io | v1.16.5 | cert-manager | Certificate management |
| 30 | envoy-gateway | docker.io/envoyproxy | v1.7.0 | envoy-gateway-system | Envoy Gateway API controller |
| 30 | reloader | stakater.github.io/stakater-charts | v1.0.10 | reloader | ConfigMap/Secret reload watcher |
| 45 | environment | Team gitops repository | HEAD | (cluster)-environment | Environment app-of-apps for workloads |
| 100 | registry | gitops repository | HEAD | argocd | Registry app-of-apps for the cluster |
Civo workload clusters have a lighter footprint than AWS workload clusters. DNS and secrets management are handled at the management cluster level rather than per workload cluster.