LogoLogo
Bonsai (0.13) DocsGitHubDiscord CommunityGarden Enterprise
Bonsai (0.13)
Bonsai (0.13)
  • Welcome to Garden!
  • 🌸Overview
    • How Garden Works
    • Core Concepts
    • Adopting Garden
    • Garden vs Other Tools
  • 🌳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
  • 🌻Getting Started
    • Quickstart Guide
    • Installing Garden
    • 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
  • 🌿Using Garden
    • About
    • Configuration Overview
    • Projects
    • Dashboard
    • Actions
    • Tests
    • Runs
    • Workflows
    • Variables and templating
    • Config Templates
    • Using the CLI
    • Modules
  • Kubernetes Plugins
    • About
    • Remote K8s Plugin Configuration
      • 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
    • Local K8s Plugin Configuration
      • 1. Install Local Kubernetes
      • 2. Configure the Provider
    • Ephemeral K8s Plugin Configuration
      • 1. Configure the Provider
      • 2. Login to the Garden dashboard
      • 3. Configure Ingress (optional)
      • 4. Retrieve Kubeconfig (optional)
    • Actions
      • Build
        • Container
      • Deploy
        • Kubernetes
        • Helm
        • Container
        • PersistentVolumeClaim
        • ConfigMap
      • Run and Test
        • Kubernetes Pod
        • Helm Pod
        • Kubernetes Exec
        • Container
    • Guides
      • In-Cluster Building
      • Minimal RBAC Configuration for Development Clusters
      • Deploying to Production
      • Using a Registry Mirror
  • ☘️Terraform Plugin
    • About
    • Plugin Configuration
    • Actions
  • 🌹Pulumi Plugin
    • About
    • Plugin Configuration
    • Actions
  • 🌼Other Plugins
    • Container
    • Exec (local scripts)
  • 🌷Guides
    • Migrating to Bonsai
    • Migrating from Docker Compose to Garden
    • Deprecations and updating to Cedar
    • Code Synchronization
    • Connecting a local application to a Kubernetes cluster (Local Mode)
    • Environments and namespaces
    • Using Garden in CircleCI
  • 🪷Advanced
    • Using Remote Sources
    • Custom Commands
  • 🎋Reference
    • Providers
      • conftest-container
      • conftest-kubernetes
      • conftest
      • container
      • ephemeral-kubernetes
      • exec
      • hadolint
      • jib
      • kubernetes
      • local-kubernetes
      • octant
      • otel-collector
      • pulumi
      • terraform
    • Action Types
      • Build
        • container Build
        • exec Build
        • jib-container Build
      • Deploy
        • configmap Deploy
        • container Deploy
        • exec Deploy
        • helm Deploy
        • kubernetes Deploy
        • persistentvolumeclaim Deploy
        • pulumi Deploy
        • terraform Deploy
      • Run
        • container Run
        • exec Run
        • helm-pod Run
        • kubernetes-exec Run
        • kubernetes-pod Run
      • Test
        • conftest-helm Test
        • conftest Test
        • container Test
        • exec Test
        • hadolint 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
    • Module Template Configuration
    • Module Types
      • configmap
      • conftest
      • container
      • exec
      • hadolint
      • helm
      • jib-container
      • kubernetes
      • persistentvolumeclaim
      • pulumi
      • templated
      • terraform
  • 🌸Misc
    • FAQ
    • Troubleshooting
    • Telemetry
    • New Garden Cloud Version
  • 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

Was this helpful?

  1. Misc

New Garden Cloud Version

PreviousTelemetryNextContributing to Garden

Last updated 1 month ago

Was this helpful?

This is an early draft that we're sharing with our community. We'll also publish a more formal announcements around the launch itself.

On March 24th, we’re rolling out a brand-new version of Garden Cloud on !

This update brings access to our Remote Container Builder, which can . Until now, this feature has only been available on our Enterprise tier—now, everyone can take advantage of its power and get faster builds.

We’re also introducing the new Garden Team Tier which replaces the current single-user dashboard and enables you to easily collaborate with your team and share test caches across environments.

What to expect

The new Team Tier will look quite a bit different from the current version and come with new capabilities. In the first iteration, we’re specifically focusing on helping teams spend less time waiting on container builds.

With the new "Builds" UI, you’ll be able to analyze where your container builds are spending the most time. Plus, our Remote Container Builder allows your entire team to benefit from blazing-fast build compute instances, caching the results of the layers of your Dockerfile on low-latency, high-throughput NVMe storage.

We're also introducing team-wide Test and Run caches for kubernetes actions that can be shared across Kubernetes clusters. Previously these caches were stored in ConfigMaps in the respective cluster and could not be shared. This approach also caused maintenance and reliability issues as the ConfigMaps grew in size. Now this data is stored hassle-free in Garden Cloud.

One temporary change to note: in this first release, command results and logs won’t be displayed as they are in the current version. But don’t worry—we’re working hard to bring them back as soon as possible! We’re a small team, and this approach lets us focus on improving the most impactful parts of the product first. We truly appreciate your patience during this transition. 🙂

In general we’re investing heavily in the new Garden Cloud product and you can expect to see rapid improvements. As much as we like the current version, it has always been a little underdeveloped and we can’t wait to deliver a polished and robust experience with the new one.

To use the new cloud version after the release, you’ll need update to Garden to version 0.14 and sign in again at . We’ll be adding more docs and content as we get closer to launch.

Impact

If you’re logged into using older versions of the Garden CLI, you’ll see a warning message saying that your command results won’t be available in Garden Cloud. Other than that, Garden will continue to work as expected—the only difference is that logs and command results won’t be visible in the UI.

Again, we’re actively working to restore this functionality while making the new Garden Cloud a vastly better experience overall.

Stay tuned, and if you have any questions, don’t hesitate to reach out or directly to ❤️

🌸
app.garden.io
dramatically accelerate container builds
app.garden.io
app.garden.io
app.garden.io
on Discord
ricky@garden.io