Google Cloud Terraform Policy Validation vs KubeLinter
Google Cloud Terraform Policy Validation
docs.cloud.google.comKubeLinter
docs.kubelinter.ioSide by side
| Figure | Google Cloud Terraform Policy Validation | KubeLinter |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Infrastructure Policy as Code Tools | 8.5 (#6) | 7.6 (#14) |
| Integrations | Google Cloud IaC validation can be run through Google Cloud CLI or integrated with Cloud Build, Jenkins, and GitHub Actions. | The project documents use with pre-commit hooks, a Docker-based pre-commit hook, and a GitHub Action for CI. |
Plans
Google Cloud Terraform Policy Validation
- gcloud beta terraform vetFree
In their own words
Google Cloud Terraform Policy Validation
Google Cloud Terraform Policy Validation checks Terraform plans against organizational security and governance constraints before infrastructure changes are applied. The `gcloud beta terraform vet` command evaluates Terraform plan JSON, retrieving project data through Google Cloud APIs. It can flag violations, issue warnings, or halt a deployment before production; it returns exit code 0 when no violations are found and 2 when they are. Platform teams can place validation between plan and apply in CI/CD workflows using Cloud Build, Jenkins, or GitHub Actions. The command accepts Terraform 0.12 or later plan JSON and requires a policy library and the Google Cloud CLI `terraform-tools` component. Policies can cover supported resources from Terraform's google and google-beta providers, and constraints can be reused with other tools that support the framework. The command is free and client-side. The feature is in Preview under Pre-GA terms, where support may be limited. Security Command Center IaC validation has separate requirements: Premium or Enterprise activation at the organization level and a specified role. That workflow also requires Terraform Google provider version 5.5 or later.
KubeLinter
KubeLinter analyzes Kubernetes YAML, Helm charts, and Kustomize manifests for configuration practices related to security and production readiness. Its default checks flag issues such as containers running as root, insufficiently limited privileges, and sensitive data stored outside secrets. Teams can turn checks on or off and define custom checks to reflect their own policies, using YAML configuration and CEL expressions. It can lint individual Kubernetes YAML files or Helm and Kustomize directories. Failed checks include remediation recommendations and produce a non-zero exit code, which can make them useful in automated workflows. Results can be written as plain text, JSON, or SARIF, including more than one format in a run. The project documents integrations with pre-commit hooks and GitHub Actions, plus installation through Go, release binaries, package managers, nix-shell, or Docker. It runs on Linux, macOS, or in a self-hosted setup. KubeLinter is free under Apache License 2.0; its documentation notes that commands, flags, and configuration formats may change.