Garden — DevOps Automation for Kubernetes Development and Testing

Introduction

Garden is an open-source DevOps automation platform that models your entire stack — services, tasks, tests — as a dependency graph and executes builds, deployments, and tests with smart caching. It targets teams developing microservices on Kubernetes who need fast feedback loops without maintaining complex CI scripts. Garden watches for file changes, rebuilds only affected components, and syncs code to remote clusters in real time.

What Garden Does

• Models multi-service stacks as a DAG with explicit dependencies between builds, deploys, and tests
• Provides incremental builds that skip unchanged components using content-based hashing
• Syncs source code to running containers in remote Kubernetes clusters for live reloading
• Runs integration and end-to-end tests as first-class graph nodes with dependency ordering
• Caches build and test results across the team using a shared remote cache

Architecture Overview

Garden runs as a CLI that reads declarative YAML configs (garden.yml) from each module directory. It constructs a dependency graph of actions: build, deploy, run, and test. The graph solver determines the execution order, checks a cache, and dispatches uncached actions to plugins. The Kubernetes plugin handles Helm and raw manifest deployments. Code sync uses Mutagen to mirror local files into remote pods. A dashboard UI visualizes the graph, logs, and action status.

Self-Hosting & Configuration

• Install the CLI via shell script, Homebrew, or npm; no server component required
• Define modules in garden.yml files at each service root with build and deploy configs
• Configure the Kubernetes provider with cluster context, namespace, and build mode
• Enable code syncing with sync config for hot-reloading source changes into running pods
• Set up remote caching with Garden Cloud or S3-compatible storage for team-wide cache sharing

Key Features

• Smart caching skips unchanged builds and tests using content hashing of source files
• Live code sync enables sub-second feedback by streaming file changes to remote pods
• Graph-based execution runs only the affected slice of your stack on each change
• Test orchestration runs integration tests with correct service dependency ordering
• Multi-environment support deploys to dev, staging, and CI with the same config

Comparison with Similar Tools

• Skaffold — file sync and build; Garden adds graph-based caching and test orchestration
• Tilt — live development focus; Garden provides broader CI/CD pipeline integration
• DevSpace — simpler dev-only tool; Garden supports full test and deploy workflows
• Telepresence — intercepts traffic locally; Garden syncs code to remote pods instead

FAQ

Q: Does Garden replace my CI/CD pipeline? A: Garden can run in CI as a build and test executor, but many teams use it for development and keep their existing CI for production deploys.

Q: Does it work with Helm charts? A: Yes. The Kubernetes plugin supports Helm charts, raw manifests, and Kustomize as deploy types.

Q: How does code sync differ from rebuilding? A: Code sync uses Mutagen to mirror file changes into running pods without rebuilding the container image, giving sub-second feedback for interpreted languages.

Q: Is Garden free? A: The CLI and core plugins are open source (MPL-2.0). Garden Cloud offers team caching and a dashboard as a commercial add-on.

Sources

• https://github.com/garden-io/garden
• https://docs.garden.io