What is Garden
Last updated
Was this helpful?
Edge Release
Last updated
Was this helpful?
Garden is a DevOps automation tool for developing and testing Kubernetes apps faster. It ties together all the components of your stack—infrastructure, builds, services, tests—into a graph of actions that fully describe how your system is built, deployed, and tested.
This lets you spin up production-like environments for development, testing, and CI on demand. It also enables teams to use the same configuration and workflows for every stage of software delivery—and dramatically speeds up builds and test runs via smart graph-aware caching.
Garden is for teams that run their workloads on Kubernetes and want a better experience around developing and testing. It assumes you have access to a Kubernetes cluster (either local or remote) and the configuration needed to build and deploy your services (i.e. Dockerfiles, manifests, Helm charts, etc).
Garden is used by:
Platform Engineers who use Garden as an integral component of their internal development platform (IDP). Garden allows them to standardize configuration and workflows across teams with heterogeneous tech stacks and to abstract away the gnarly bits so that feature teams can focus on the fun stuff ().
DevOps Engineers who use Garden to build fast and portable CI pipelines ().
Application Developers who use Garden to develop and test in production-like environments that they can spin up on-demand, without waiting for CI ().
Garden Core is a standalone binary that can run from CI or from a developer’s machine. Its configuration framework allows you to codify a complete description of your stack using intuitive YAML declarations—making your workflows reproducible and portable.
Here's an example of simplified Garden config:
Garden collects all of these descriptions, even across multiple repositories, into the Stack Graph—an executable blueprint for going from zero to a running system in a single command.
Garden then leverages your existing configuration (Helm charts, Kubernetes manifests, Dockerfiles, Terraform files, etc) and infrastructure to execute the graph in any environment.
Each of the four action kinds (Build, Deploy, Test, Run) has a corresponding command that you can run with the Garden CLI.
For example, to create a preview environment on every pull request, simply add the following to your CI pipeline:
Or say a developer wants to run an end-to-end test from their laptop as they code. Again, it’s simple:
Garden also has a special mode called "sync mode" which live syncs changes to your running deploys ensuring blazing fast feedback while developing. To enable it, simply run:
There are also utility commands for getting logs, exec-ing into services, publishing images, and more.
No matter how big your stack grows, these workflows stay consistent.
One of the most important features of Garden is its smart caching abilities. Thanks to the graph structure, Garden can calculate the version of any part of your system, while accounting for upstream dependencies.
This ensures that the same image never needs to be built twice or the same test run twice.
If the end-to-end test in the example above passes, Garden will know not to run it again if the code hasn’t changed. Since Garden factors in dependencies, it will however re-run the test if any of the upstream services under test are modified.
Most tools don’t have this granular understanding of the system and the choice is between running everything or nothing. With Garden you can be confident that tests run when they need to, but no more.
This alone can speed up your pipelines by orders of magnitude.
Garden has a powerful templating engine that allows you to set variables and enable or disable parts of the graph depending on your environment.
You might for e.g. deploy a development database with the Kubernetes plugin in development but use the Terraform plugin to provision a managed database for production.
This allows you to codify your entire stack and use the same workflows for all stages of software delivery.