Huawei CloudPlan-validated

Huawei Cloud CCE Cluster

CCE Kubernetes with VPC/subnet, node pool, and EIP-attached ingress.

terraformAlt & Specialty Cloudshuaweicloud

Compare Managed Kubernetes across clouds →

huawei-cce-clustervizier v1.2.0

Verification

Plan-validated

Passed: 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

Functional

  • Live test pending (no cloud run yet)

Last verified 2026-06-28 · how we verify

Verify this download

cosign · sha-256

Don'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 huawei-cce-cluster-1.0.0.sigstore.json \
  https://www.iac-bazaar.com/api/artifacts/huawei-cce-cluster/signature

# 3. Verify the tarball you downloaded
cosign verify-blob \
  --key cosign.pub \
  --bundle huawei-cce-cluster-1.0.0.sigstore.json \
  huawei-cce-cluster-1.0.0.tar.gz
# → Verified OK

# 4. (optional) confirm the checksum too
echo "1c9d6d42d1d926ccf1362f190d2f4f167d66a491f63e859cd977d78495d2efd6  huawei-cce-cluster-1.0.0.tar.gz" | sha256sum -c

Use it from the registry

terraform · opentofu
module "cce_cluster" {
  source  = "www.iac-bazaar.com/iac-bazaar/huawei-cce-cluster/huaweicloud"
  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 · attribution

Paste 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.

README.md, GitLab, Gitea
[![IaC Bazaar: plan-validated](https://www.iac-bazaar.com/api/artifacts/huawei-cce-cluster/badge)](https://www.iac-bazaar.com/catalog/huawei-cce-cluster?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

Terraform module 1.0.0, plan-validated on IaC Bazaar: [Huawei Cloud CCE Cluster](https://www.iac-bazaar.com/catalog/huawei-cce-cluster?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

```hcl
module "cce_cluster" {
  source  = "www.iac-bazaar.com/iac-bazaar/huawei-cce-cluster/huaweicloud"
  version = "1.0.0"
}
```

Preview:IaC Bazaar: plan-validated

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

huawei-cce-cluster

A production-ready Huawei Cloud CCE (Cloud Container Engine) managed Kubernetes cluster. The module owns its network end to end — it creates the VPC and a DNS-enabled node subnet, stands up the CCE control plane, and attaches autoscaling worker node pools with KMS-encryptable disks.

Status: static-validated, live-test pending. Validated with tofu validate + tflint + checkov against the huaweicloud/huaweicloud provider. Not yet applied against a live Huawei Cloud account (no sandbox subscription; CCE clusters take ~10-15 min to create and bill a per-cluster fee), so it ships under live-test quarantine.

Design & secure defaults

  • Private API server. No public EIP is bound by default (eip = null) — the Kubernetes API server is reachable only from inside the VPC (use a bastion, VPN, or Direct Connect). Bind an EIP explicitly only if you must reach it from the internet.
  • Secrets envelope encryption. Pass kms_key_id to encrypt Kubernetes Secrets at rest in etcd via a customer-managed KMS key (encryption_config mode = KMS). Recommended for regulated workloads.
  • Encrypted worker disks. Node-pool root and data volumes accept a kms_key_id for at-rest encryption; data volumes default to a 100 GB SSD.
  • Storage retained on destroy. delete_all_on_destroy = "false" so a Terraform destroy cannot silently delete associated EVS/SFS/OBS volumes. Flip to "true"/"try" only when you intend a full cleanup.
  • HA control plane. On the s2 flavors you can spread masters across three AZs (master_availability_zones) for an availability-zone-resilient control plane. The s2 family is the production default.
  • RBAC by default (authentication_mode = "rbac") and ipvs kube-proxy for service scalability.
  • Key-pair login only. Node pools authenticate via an SSH key_pair name — no plaintext passwords are accepted into Terraform state.
  • Production CNI. vpc-router by default (VPC-routed pod IPs); choose eni (CCE Turbo) for per-pod ENIs and Kubernetes NetworkPolicy / security groups.

Cross-field invariants (HA masters need an s2 flavor; autoscaling needs min <= max; data volumes ≥ 10 GB; valid taint effects) are enforced with precondition/validation blocks, so misconfigurations fail at plan time.

Provider

huaweicloud/huaweicloud >= 1.0, < 2.0. 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