IBM Cloud Kubernetes (IKS) on VPC
IKS cluster on VPC Gen2 with worker pools and COS-backed registry namespace.
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 ibm-iks-cluster-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/ibm-iks-cluster/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle ibm-iks-cluster-1.0.0.sigstore.json \
ibm-iks-cluster-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "21e07fb954a72e5e6a72848d00516af7630247ddb4da7c6d1f07cd79f7633280 ibm-iks-cluster-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "iks_cluster" {
source = "www.iac-bazaar.com/iac-bazaar/ibm-iks-cluster/ibmcloud"
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/ibm-iks-cluster?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, plan-validated on IaC Bazaar: [IBM Cloud Kubernetes (IKS) on VPC](https://www.iac-bazaar.com/catalog/ibm-iks-cluster?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "iks_cluster" {
source = "www.iac-bazaar.com/iac-bazaar/ibm-iks-cluster/ibmcloud"
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
ibm-iks-cluster
IBM Cloud Kubernetes Service (IKS) on VPC Gen2 — a managed Kubernetes
cluster with a multizone default worker pool, optional additional worker pools,
a COS-backed Container Registry namespace for private images, and an optional
dedicated Cloud Object Storage instance. Works with Terraform and OpenTofu
(>= 1.6), IBM Cloud provider >= 2.0, < 3.0.
Status: static-validated, live-test pending. This module ships under live-test quarantine — IKS provisioning takes ~20 minutes and requires a paid IBM Cloud account, so the real apply → verify → destroy gate runs once a cloud sandbox is available. The configuration is validated with
tofu fmt,tofu validate, andtflint.
Secure defaults
- Private-only Kubernetes API —
disable_public_service_endpoint = trueby default; the master is reachable only over the VPC private service endpoint. - Customer-managed secrets encryption — wire Key Protect / Hyper Protect
Crypto Services through
kms_configto encrypt the cluster's etcd secrets with your own root key; KMS traffic stays on the private endpoint by default. - Multizone by design — supply three zones for an HA control plane and
worker spread; each zone places
worker_countnodes. - Persistent storage preserved on destroy —
force_delete_storage = falseby default so block volumes survive an accidentaldestroy. - No hardcoded secrets — the IBM API key is supplied to the provider, never to the module.
Requirements
- Terraform or OpenTofu
>= 1.6 IBM-Cloud/ibmprovider>= 2.0, < 3.0- An IBM Cloud paid account with VPC Infrastructure and Kubernetes Service
access, and an API key supplied to the provider (
ibmcloud_api_key).
License
Commercial — LicenseRef-IaCBazaar-Commercial. © IaC Bazaar. Original work (not derived from a third-party module).
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
- Inputs
- Outputs
- Notes
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.