Exoscale SKS Cluster
SKS Kubernetes with node pools, security groups, and anti-affinity.
Verification
Plan-validatedPassed: module logic verified on a mocked plan - inputs, validation rules, conditional creation and outputs resolve (no real provider, no cloud).
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 exoscale-sks-cluster-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/exoscale-sks-cluster/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle exoscale-sks-cluster-1.0.0.sigstore.json \
exoscale-sks-cluster-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "cb71cdd685111a5d6ebf4328b5d566a66d0c1b1c45abfa0d28bc307b9e634243 exoscale-sks-cluster-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "sks_cluster" {
source = "www.iac-bazaar.com/iac-bazaar/exoscale-sks-cluster/exoscale"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads plan-validated because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/exoscale-sks-cluster?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, plan-validated on IaC Bazaar: [Exoscale SKS Cluster](https://www.iac-bazaar.com/catalog/exoscale-sks-cluster?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "sks_cluster" {
source = "www.iac-bazaar.com/iac-bazaar/exoscale-sks-cluster/exoscale"
version = "1.0.0"
}
```Preview:
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 module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
exoscale-sks-cluster
An Exoscale SKS managed Kubernetes cluster: an SLA-backed control plane with one or more worker node pools, a least-privilege cluster security group, and a dedicated anti-affinity group so a pool's nodes never share a hypervisor. Targets EU-sovereign zones (CH / AT / DE).
Status: static-validated, live-test pending. Validated with
tofu validate+tflint+checkovagainst theexoscale/exoscaleprovider. Not yet applied against a live Exoscale account, so it ships under live-test quarantine.
Design & secure defaults
- HA control plane by default.
service_level = "pro"provisions the SLA-backed, highly-available control plane. Use"starter"only for the free, best-effort tier. - Cilium CNI by default so Kubernetes NetworkPolicies are enforced.
- Least-privilege cluster security group. Only the intra-cluster traffic SKS requires is opened, and only between members of the group itself (self-referencing rules), not the internet: VXLAN overlay (UDP 4789 / 8472), kubelet API (TCP 10250), and Cilium agent health (TCP 4240).
- NodePort range closed by default. The public NodePort range
(30000-32767) is denied until you explicitly pass
nodeport_ingress_cidrs; expose services through a load balancer instead. - Anti-affinity for resilience. Every node pool is placed in a dedicated anti-affinity group so node failures don't cascade across a single host.
- CCM / CSI / metrics-server on so load balancers, block-storage PVs, and
HPA /
kubectl topwork out of the box. The CSI depends on the CCM, soexoscale_csi = truerequiresexoscale_ccm = true(enforced at plan time). - Auto-upgrade on for control-plane patch updates.
- Optional OIDC API-server authentication via the
oidcinput.
Per-pool input validation enforces minimum size (>= 1), minimum disk
(>= 20 GiB), and the <family>.<size> instance-type form. Pools with
storage_lvm = true require disk_size >= 100 GiB (the provider's
non-standard persistent-storage partitioning needs at least 100 GiB).
Provider
exoscale/exoscale ~> 0.69. Requires Terraform/OpenTofu >= 1.6.
License
Commercial — LicenseRef-IaCBazaar-Commercial. See the IaC Bazaar terms.
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
- Key inputs
- Outputs
Related modules
upcloud-kubernetes
An UpCloud Managed Kubernetes cluster whose API answers only the ranges you list (0.0.0.0/0 by name), with private node groups off the public internet, node storage encrypted at rest (unencrypted by name), anti-affinity across hosts, manual upgrades, and node groups from a map with labels and taints. The plan is the control plane's redundancy and bill.
alicloud-ack-cluster
Managed ACK Kubernetes with node pools, VPC integration, and RAM roles.
azure-aks
Hardened AKS with system/user node pools, workload identity, Entra RBAC integration, Azure CNI overlay, and Container Insights wired in.
civo-k3s-cluster
Fast-launch k3s cluster with node pools, firewall rules, and network.
do-doks-cluster
Production DOKS with node pools, VPC, registry hookup, and maintenance windows in one apply.
aws-eks
Opinionated EKS cluster with node groups, core add-ons, Pod Identity, and KMS secret encryption.