GlossaryTerraform

Terraform

Terraform is an infrastructure-as-code tool from HashiCorp that lets teams define cloud, network, and Kubernetes resources in configuration files and provision them automatically.

Table of Contents

Table of Contents

How Terraform works

Teams describe the desired infrastructure in HashiCorp Configuration Language (HCL). Terraform figures out what to create, change, or delete.

  1. Write: define resources in .tf files.
  2. Init: download the providers the configuration needs.
  3. Plan: preview exactly what will change.
  4. Apply: make the changes and record them in state.
  5. Destroy: tear down resources when no longer needed.

Key Terraform concepts

  • Providers: plugins for AWS, Google Cloud, Azure, Kubernetes, Helm, and more
  • Resources: the infrastructure objects Terraform manages
  • State: a record of what Terraform has created
  • Modules: reusable groups of resources
  • Variables: inputs that customize a configuration per environment

Terraform vs. Helm

Teams often use both. They work at different layers.

Terraform Helm
Scope Clouds, networks, clusters, and more Apps inside Kubernetes
Language HCL Templated YAML
State Tracked in a state file Tracked as releases in the cluster
Typical use Create the cluster Deploy software onto it

Why Terraform matters

Terraform makes infrastructure consistent, repeatable, and version-controlled.

  • Repeatability: the same files build the same environment every time
  • Reviewable changes: plans show changes before they happen
  • Multi-cloud: one workflow across many providers
  • Modules: reusable building blocks across teams
  • Auditability: Git history shows who changed what

Consider a SaaS team that needs a fresh test cluster for each major release. With Terraform, one command builds it, including networking, the cluster, and testing tools.

Common challenges with Terraform

  • State management: shared state needs locking and secure storage
  • Drift: manual changes break the match between code and reality
  • Module sprawl: too many custom modules get hard to maintain
  • Secrets: sensitive values must stay out of plain-text state and code
  • Licensing: Terraform uses a source-available license; OpenTofu is an open-source fork

How Terraform relates to Testkube

Testkube fits into Terraform-managed infrastructure. Testing becomes part of how environments are built.

  • Automated deployment: install and configure Testkube as part of Terraform runs
  • Scalable environments: provision Testkube across regions or projects with modules
  • Version control: Terraform code for Testkube lives in Git for GitOps and audits
  • Simple onboarding: new clusters get Testkube and its dependencies in one apply
  • Post-provision tests: pipelines can trigger Testkube after each Terraform change

Frequently Asked Questions (FAQs)

Can I deploy Testkube using Terraform?

Yes. Teams commonly install Testkube through Terraform, often with the Helm provider.

What providers does Terraform support for Testkube deployment?

The Kubernetes and Helm providers are typical, alongside cloud providers that create the cluster.

How does Terraform improve Testkube setup?

It makes installation repeatable and versioned across every cluster and environment.

Can I manage Testkube updates through Terraform?

Yes. Change the version in code and apply it to roll out the update.

Is Terraform required to use Testkube?

No. Testkube also installs with Helm, the CLI, or GitOps tools.

Is Terraform open source?

Terraform now uses a source-available license. OpenTofu is a community-maintained open-source fork.

Related Terms and Concepts

No items found.