Civo Kubernetes Cluster
Fast-launch k3s cluster with node pools, firewall rules, and network.
Verification
Static-verifiedPassed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).
Conformance
- Static validation (fmt · validate · tflint)
- No applicable security policies for this provider
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live test pending (no cloud run yet)
Last verified 2026-06-28 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o civo-k3s-cluster-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/civo-k3s-cluster/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle civo-k3s-cluster-1.0.0.sigstore.json \
civo-k3s-cluster-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "6a5aba69d4fe33b10a19d8a5181ef929103a60d0f7673ca636b0cfd21843dcac civo-k3s-cluster-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "k3s_cluster" {
source = "www.iac-bazaar.com/iac-bazaar/civo-k3s-cluster/civo"
version = "1.0.0"
}Paid module — needs a purchase (or a subscription that covers it) plus a registry token from /account/tokens. Full setup: registry docs.
Inputs & outputs
Create a free account to read this module's contract
The declared contract — every input name, type, default and description, plus every output — is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every Free module. This one is Premium, so its contract unlocks when you buy it.
Documentation
civo-k3s-cluster
Status: static-validated, live-test pending. This module ships under live-test quarantine — it passes
tofu fmt,tofu validate, andtflint, but the real apply → verify → destroy gate is deferred until a Civo cloud sandbox account is wired into the live-test lane. Treat the secure defaults as reviewed, the cloud behavior as not yet proven end-to-end.
Fast-launch Civo Kubernetes (k3s) cluster on a
dedicated private network behind a deny-by-default firewall, with a required
built-in node pool plus optional standalone pools. Civo clusters boot in roughly
90 seconds, making this the fastest live-test k8s lane in the catalog. Works
with Terraform and OpenTofu (>= 1.6), Civo provider >= 1.0, < 2.0.
Design / secure defaults
- Dedicated private network (
civo_network) per cluster instead of the Civo default network — clean blast-radius isolation. - Deny-by-default firewall. The
civo_firewallis created withcreate_default_rules = false, so nothing inbound is permitted until you list CIDRs. The Kubernetes API (tcp/6443) opens only forapi_allowed_cidrs; an empty list (the default) leaves the API unreachable rather than world-open. Web ports (80/443) open only foringress_allowed_cidrs. Egress is allowed so nodes can pull images and reach the control plane. - One required inline pool + standalone extras. Civo mandates exactly one
inline
poolsblock on the cluster resource; this module exposes it asdefault_pooland adds further pools as independentcivo_kubernetes_node_poolresources so you can churn capacity without recreating the cluster. - CNI choice.
flannelby default; setcni = "cilium"to get NetworkPolicy enforcement. - Kubeconfig is a sensitive output and never printed in plan/apply logs.
Requirements
- Terraform or OpenTofu
>= 1.6 civo/civoprovider>= 1.0, < 2.0- Civo mandates exactly one inline pool —
default_poolis always created. Useextra_node_poolsfor pools you expect to add/remove. kubernetes_versionupgrades recycle nodes.
License
Commercial — LicenseRef-IaCBazaar-Commercial.
Usage code & full reference unlock after purchase
The complete copy-paste usage, the full input/output reference, and operational notes ship with your licence - shown here and bundled in the download.
- Usage
- Inputs
- Outputs
Related modules
Alibaba Cloud ACK Cluster
Managed ACK Kubernetes with node pools, VPC integration, and RAM roles.
Azure Kubernetes Service Cluster
Hardened AKS with system/user node pools, workload identity, Entra RBAC integration, Azure CNI overlay, and Container Insights wired in.
DigitalOcean DOKS Cluster
Production DOKS with node pools, VPC, registry hookup, and maintenance windows in one apply.
EKS Cluster with Managed Node Groups
Opinionated EKS cluster with node groups, core add-ons, Pod Identity, and KMS secret encryption.
Exoscale SKS Cluster
SKS Kubernetes with node pools, security groups, and anti-affinity.
GKE Cluster (Autopilot & Standard)
Private, Workload-Identity-enabled GKE cluster with managed node pools, release channels and maintenance windows, hardened to Google best practice.