Linode NodeBalancer Load Balancer
Managed L4/L7 load balancer with TLS termination, health checks, session stickiness, and UDP support.
Verification
Static-verifiedPassed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- 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 linode-nodebalancer-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/linode-nodebalancer/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle linode-nodebalancer-1.0.0.sigstore.json \
linode-nodebalancer-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "60ddba59a2248f6c86dea6416333e5707b6e7aa9c07dff23663529c0bb22c5c7 linode-nodebalancer-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "nodebalancer" {
source = "www.iac-bazaar.com/iac-bazaar/linode-nodebalancer/linode"
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 Professional, so its contract unlocks when you buy it.
Documentation
linode-nodebalancer
Managed Linode NodeBalancer (L4/L7 load balancer) with TLS-terminating HTTPS
listeners, active health checks, session stickiness, and optional VPC-backed
backends — in one apply. Works with Terraform and OpenTofu (>= 1.6),
Linode provider >= 3.14, < 4.0.
Status: static-validated, live-test pending. This module ships under live-test quarantine: it has passed
tofu fmt,tofu validate, andtflint, but the real apply → verify → destroy gate is pending a Linode sandbox account. Treat the secure defaults below as the contract.
Design & secure defaults
- HTTPS by default. A config's
protocoldefaults tohttps, and the module requiresssl_cert+ssl_keyfor HTTPS listeners (enforced with a plan-time precondition). TLS material issensitive. - Modern ciphers only.
cipher_suiteis pinned torecommended; thelegacysuite (weak ciphers) is rejected by variable validation — opt-in would require a custom build, not a flag. - Health checking on by default. Every config gets active checks
(
check = "connection") plus passive checks (check_passive = true), so a failed backend is pulled out of rotation automatically. - Private-IP backends only. Every node
addressmust be an RFC1918 private IP (validated). Public-IP backends are rejected — backend traffic stays on the private/VPC network. - proxy_protocol is TCP-scoped. The module silently neutralizes
proxy_protocolon non-TCP configs so it can't be misapplied. - Firewalls stay out-of-band. Attach a Cloud Firewall via the
linode-firewallmodule (linode_firewall_device) so rules and balancer lifecycle are decoupled. - Optional VPC backends.
vpc_backendroutes backend traffic over a VPC subnet (newer NodeBalancer feature) instead of the legacy private network.
Requirements
- Terraform or OpenTofu
>= 1.6 linode/linodeprovider>= 3.14, < 4.0- Backend nodes must already exist and be reachable on a private IP (or VPC subnet) before the balancer can mark them healthy.
- VPC-backed backends are a newer Linode feature; confirm regional availability.
License
Commercial — LicenseRef-IaCBazaar-Commercial. © IaC Bazaar. Original work
(not derived from a third-party module).
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
Application Gateway v2 + WAF
Regional L7 load balancer with WAF v2 policy, TLS termination from Key Vault, autoscaling and health probes.
Application Load Balancer
ALB with HTTPS listeners, target groups, listener rules, and access logging - drop-in for ECS/EC2/Lambda targets.
Azure Standard Load Balancer (L4)
An Azure Standard L4 load balancer with a self-created static public IP frontend, a backend address pool, health probes and load-balancing rules - Standard SKU throughout.
Flexible Load Balancer (L7)
HTTPS load balancer with backend sets, health checks, TLS certificates, rule sets and WAF-ready listeners.
Global External HTTPS Load Balancer
Global ALB with managed TLS certs, URL map, serverless/instance NEG backends, optional Cloud CDN and Cloud Armor policy.
Hetzner Load-Balanced Web Tier
Managed LB with health checks, cert, and label-selected server targets.