LogoLogo
Bonsai (0.13) DocsGitHubDiscord CommunityGarden Enterprise
Edge Release
Edge Release
  • Welcome to Garden!
  • Overview
    • What is Garden
    • Use Cases
      • Isolated On-Demand Preview Environments
      • Fast, Portable CI Pipelines that Run Anywhere
      • Shift Testing Left
      • Local Development With Remote Clusters
      • Jumpstart your Internal Developer Platform
    • Garden vs Other Tools
  • Getting Started
    • Quickstart
    • Garden Basics
    • Next Steps
  • Tutorials
    • Your First Project
      • 1. Create a Garden Project
      • 2. Pick a Kubernetes Plugin
      • 3. Add Actions
      • 4. Add Tests
      • 5. Code Syncing (Hot Reload)
      • 6. Next Steps
    • Setting up a Kubernetes cluster
      • 1. Create a Cluster
        • AWS
        • GCP
        • Azure
      • 2. Configure Container Registry
        • AWS
        • GCP
        • Azure
        • Docker Hub
      • 3. Set Up Ingress, TLS and DNS
      • 4. Configure the Provider
  • Using Garden With
    • Containers
      • Using Remote Container Builder
      • Building Containers
    • Kubernetes
      • Using Remote Kubernetes
      • Using Local Kubernetes
      • Deploying K8s Resources
      • Installing Helm charts
      • Running Tests and Tasks
    • Terraform
      • Using Terraform
      • Applying Terrform Stacks
    • Pulumi
      • Using Pulumi
      • Applying Pulumi Stacks
    • Local Scripts
  • Features
    • Remote Container Builder
    • Team Caching
    • Variables and Templating
    • Config Templates
    • Workflows
    • Code Synchronization
    • Custom Commands
    • Remote Sources
  • Guides
    • Connecting a Project
    • Environments and Namespaces
    • Installing Garden
    • Including/Excluding files
    • Installing Local Kubernetes
    • Migrating from Docker Compose to Garden
    • Using the CLI
    • Using Garden in CircleCI
    • Minimal RBAC Configuration for Development Clusters
    • Deploying to Production
    • Using a Registry Mirror
  • Reference
    • Providers
      • container
      • exec
      • jib
      • kubernetes
      • local-kubernetes
      • otel-collector
      • pulumi
      • terraform
    • Action Types
      • Build
        • container Build
        • exec Build
        • jib-container Build
      • Deploy
        • container Deploy
        • exec Deploy
        • helm Deploy
        • kubernetes Deploy
        • pulumi Deploy
        • terraform Deploy
      • Run
        • container Run
        • exec Run
        • helm-pod Run
        • kubernetes-exec Run
        • kubernetes-pod Run
      • Test
        • container Test
        • exec Test
        • helm-pod Test
        • kubernetes-exec Test
        • kubernetes-pod Test
    • Template Strings
      • Project template context
      • Environment template context
      • Provider template context
      • Action (all fields) template context
      • Action spec template context
      • Module template context
      • Remote Source template context
      • Project Output template context
      • Custom Command template context
      • Workflow template context
      • Template Helper Functions
    • Commands
    • Project Configuration
    • ConfigTemplate Reference
    • RenderTemplate Reference
    • Workflow Configuration
    • Garden Containers on Docker Hub
    • Glossary
    • Module Template Configuration
    • Module Types
      • container
      • exec
      • helm
      • jib-container
      • kubernetes
      • pulumi
      • templated
      • terraform
  • Misc
    • FAQ
    • Troubleshooting
    • Telemetry
    • How Organizations Adopt Garden
    • New Garden Cloud Version
    • Migrating to Cedar
    • Migrating to Bonsai
    • Ingress NGINX Vulnerability
    • Deprecations
  • Contributing to Garden
    • Contributor Covenant Code of Conduct
    • Contributing to the Docs
    • Setting up Your Developer Environment
    • Developing Garden
    • Config Resolution
    • Graph Execution
Powered by GitBook
On this page
  • What’s new
  • What’s changed
  • How to update

Was this helpful?

  1. Misc

Migrating to Cedar

PreviousNew Garden Cloud VersionNextMigrating to Bonsai

Last updated 2 months ago

Was this helpful?

Big news! We’re releasing Garden 0.14 and launching the next generation of Garden Cloud—the first step in a huge evolution for Garden.

What’s new

  • – No more slow local builds! Now, every Garden Cloud user gets access to powerful remote build acceleration, previously only available on our Enterprise plan.

  • The new Garden Team Tier – A dedicated, collaborative experience for teams scaling with Garden.

  • – Cache test results across clusters and environments with team-wide caching in Garden Cloud.

  • A new Builds UI – Get deep visibility into your builds' performance and optimize with ease.

What’s changed

In 0.14, we're changing the cache backend we use for our Kubernetes-based Test and Run actions (i.e. kubernetes-pod, helm-pod and container Runs and Tests).

In 0.13 and earlier, results for these action types were cached using ConfigMaps created in the Kubernetes cluster being used. This has worked well for a long time, but came with certain problems and limitations. ConfigMaps would pile up over time, requiring administrators to periodically clean them up. Also, tests couldn't be cached across Kubernetes clusters, which made it impossible to get cache hits for tests in CI that had already been successfully run e.g. on a local Kubernetes cluster during development.

Our solution to this is to use Garden Cloud as the caching backend. This means zero maintenance for our users, and more importantly, opens the door to fully shared caching across environments. For situations when you can't log in right now, Garden falls back to a local file-based cache storage.

Our free tier includes a certain maximum number of monthly cache hits, and our Team and Enterprise tiers have higher limits. Please see our pricing page for more details.

0.14 also contains several breaking changes that are intended to make Garden easier to adopt and use.

These changes will help users configure and use Garden in the recommended way from the start. Garden is a powerful system, but it can also become as complex as the use cases it supports. We periodically streamline its configuration APIs and features to emphasize best practices and ease of use while deprecating those that have newer and better alternatives.

For users who are still on 0.13, you can prepare for upgrading to 0.14 by setting apiVersion: garden.io/v2 in your project config, running your Garden commands and addressing any warnings and errors that come up.

For a complete overview of the breaking changes in Garden 14 (Cedar), please refer to the .

How to update

If you're using 0.13 Bonsai, follow these steps:

  1. Make sure to update to the latest release using garden self-update (At least to 0.13.56).

  2. From version 0.13.56, whenever Garden detects usage of deprecated functionalities, it will print a warning message accompanied by an explainer link. To fix all the warnings, please follow all the steps as needed.

  3. In order to resolve some of the warnings, for example when we introduced new defaults or a different behaviour, you'll need to change the apiVersion setting in the project-level configuration to apiVersion: garden.io/v2.

  4. After updating the apiVersion, you can verify that your configuration still works as expected since Garden will reject use of deprecated functionalities.

Once you completed these steps, you can safely update to Garden 0.14 (Cedar) by running garden self-update.

If you are using Garden 0.12 (Acorn), please complete the first.

Remote Container Builder general access
Team-wide caching
Deprecations and migrating to Cedar guide
migration guide for Garden 0.13 (Bonsai)