Garden — DevOps Automation for Kubernetes Development and Testing

What it is

Garden is a DevOps automation tool that accelerates Kubernetes development and testing workflows. It lets you define your entire stack as a dependency graph, then handles building, deploying, and testing with fast incremental updates. Garden watches for file changes and syncs them to remote clusters in real time.

Garden targets platform engineers and backend developers who work with multi-service Kubernetes stacks where the inner development loop (code-build-deploy-test) is painfully slow.

How it saves time or tokens

Garden's dependency graph model means only changed services and their dependents rebuild and redeploy. File syncing to remote clusters replaces the full build-push-deploy cycle for iterative changes. Integrated test workflows run unit, integration, and end-to-end tests as part of the same graph, eliminating separate CI scripts. The result is inner loop times measured in seconds instead of minutes.

How to use

1. Install Garden CLI and initialize your project with garden init to generate a garden.yml configuration.
2. Define your services, builds, and tests as modules in the Garden configuration file.
3. Run garden dev to start the development loop with live reloading and automatic redeployment on file changes.

Example

# garden.yml example
kind: Module
name: api-service
type: container
build:
  command: [docker, build, -t, api-service, .]
services:
  - name: api
    ports:
      - name: http
        containerPort: 3000
tests:
  - name: unit
    command: [npm, test]
  - name: integ
    command: [npm, run, test:integ]
    dependencies:
      - api

Related on TokRepo

• DevOps tools -- more Kubernetes and infrastructure automation tools
• Automation tools -- build and deployment automation workflows

Common pitfalls

• Garden requires a running Kubernetes cluster (local or remote); it does not provision clusters itself.
• Large monorepo projects need careful module boundary definitions to keep the dependency graph efficient.
• File sync mode works best with interpreted languages; compiled languages still require container rebuilds for dependency changes.