DEV Community: Sahithi V

Manage Multiple Terraform Versions with tfswitch

Sahithi V — Mon, 20 Oct 2025 08:55:42 +0000

That’s where terraform-switcher (tfswitch) comes to the rescue.

💡 What Is `tfswitch`?

tfswitch is a simple command-line tool that helps you install and switch between different Terraform versions instantly.

You can think of it like nvm (Node Version Manager) — but for Terraform.

🚀 Why You Need It

In real-world projects, different environments or teams may lock Terraform to different versions.

For example:

A legacy infrastructure might still use Terraform 0.14
A new project might use Terraform 1.7+
A CI/CD pipeline might expect a specific version declared in .terraform-version

Instead of manually downloading .zip files, updating paths, or reinstalling Terraform every time — tfswitch makes it seamless.

⚙️ Installation

On macOS (via Homebrew):

brew install warrensbox/tap/tfswitch

On Linux:

curl -L https://raw.githubusercontent.com/warrensbox/terraform-switcher/release/install.sh | bash

On Windows (using Chocolatey):

choco install tfswitch

🧠 How It Works

tfswitch detects the Terraform version you need in three ways:

1. From `.terraform-version` file

If your project includes a .terraform-version file:

1.5.7

Just run:

tfswitch

It will automatically install and switch to that version.

2. From `required_version` in Terraform configuration

terraform {
  required_version = ">= 1.4.0"
}

tfswitch can read and match it automatically.

3. Manual Selection

tfswitch

You’ll get an interactive menu to choose your desired version:

Use the arrow keys to navigate: ↓ ↑ → ← 
Select Terraform version: 
  1.7.0
> 1.5.7
  1.4.6
  0.14.11

🧩 Real-World Example

Imagine you have two Terraform projects:

Project A (old) requires Terraform 0.14.11
Project B (new) requires Terraform 1.6.0

With tfswitch, switching between them is as simple as:

cd projectA
tfswitch 0.14.11

cd ../projectB
tfswitch 1.6.0

No path changes. No reinstallations. Just productivity.

🔁 In

How to Convert a docker-compose file to K8S manifest

Sahithi V — Fri, 17 Oct 2025 08:39:08 +0000

How to Convert a Docker Compose File to Kubernetes Manifests Using Kompose

Many of us use Docker for local development, but when it’s time to run containers on Kubernetes, converting your setup can seem daunting. Kompose makes this transition easy by converting your docker-compose.yml into Kubernetes manifests.

Below are the latest steps to get your services running on Kubernetes:

1. Install Kompose (Latest Version)

On Mac (using Homebrew):

brew install kompose

Or download the latest release manually:

curl -L https://github.com/kubernetes/kompose/releases/latest/download/kompose-darwin-amd64 -o kompose
chmod +x kompose
sudo mv ./kompose /usr/local/bin/kompose

2. Prepare Your Docker Compose File

Build and push your Docker images to a remote registry.
Update your docker-compose.yml so that each service uses the image URL from your registry (not a local build context).

Example docker-compose.yml:

version: "3"
services:
  mythical-requester:
    image: <REMOTE-IMAGE>
    ports:
      - "4001:4001"
    environment:
      - NAMESPACE=production
      - LOGS_TARGET=http://loki:3100/loki/api/v1/push
      - TRACING_COLLECTOR_HOST=agent
      - TRACING_COLLECTOR_PORT=4317
      - OTEL_EXPORTER_OTLP_TRACES_INSECURE=true
      - OTEL_RESOURCE_ATTRIBUTES=ip=1.2.3.4

  mythical-server:
    image: <REMOTE-IMAGE>
    ports:
      - "4000:4000"
      - "80:80"
    depends_on:
      - mythical-database
    environment:
      - NAMESPACE=production
      - LOGS_TARGET=http://loki:3100/loki/api/v1/push
      - TRACING_COLLECTOR_HOST=agent
      - TRACING_COLLECTOR_PORT=4317
      - OTEL_EXPORTER_OTLP_TRACES_INSECURE=true
      - OTEL_RESOURCE_ATTRIBUTES=ip=1.2.3.5

  mythical-recorder:
    image: <REMOTE-IMAGE>
    ports:
      - "4002:4002"
    environment:
      - NAMESPACE=production
      - LOGS_TARGET=http://loki:3100/loki/api/v1/push
      - TRACING_COLLECTOR_HOST=agent
      - TRACING_COLLECTOR_PORT=4317
      - OTEL_EXPORTER_OTLP_TRACES_INSECURE=true
      - OTEL_RESOURCE_ATTRIBUTES=ip=1.2.3.5

3. Convert Docker Compose to Kubernetes Manifests

Run the following command in the directory containing your docker-compose.yml:

kompose convert

Kompose will generate Kubernetes YAML files for each service, typically creating both a deployment and a service manifest per service.

4. Deploy to Kubernetes

Move all generated YAML files to a folder (e.g., deployment/):
```
mkdir deployment
mv *.yaml deployment/
```
Connect to your Kubernetes cluster (ensure kubectl is configured).
Apply all manifests:
```
kubectl apply -f deployment/
```
Check your pods:
```
kubectl get pods
```

Congratulations!

Your Docker Compose services are now running on your Kubernetes cluster.

References: