Garden 0.14.10 is out! 🎉
This release contains a variety of new features and improvements, along with a handful of bug fixes and security updates. Below are some of the key additions.
Assets
Download the Garden binary for your platform from below or simply run garden self-update if you already have it installed.
- Garden v0.14.10 for Alpine AMD64 (tar.gz)
- Garden v0.14.10 for Linux AMD64 (tar.gz)
- Garden v0.14.10 for Linux ARM64 (tar.gz)
- Garden v0.14.10 for MacOS AMD64 (tar.gz)
- Garden v0.14.10 for MacOS ARM64 (tar.gz)
- Garden v0.14.10 for Windows AMD64 (.zip)
Highlights
Automatic Environment Cleanup (”AEC”) for Kubernetes
We’ve implemented a new version of the AEC feature for Kubernetes, previously only available to Garden Enterprise customers.
With this, you can configure your Kubernetes namespaces to be automatically paused and/or cleaned up based on your preferences, on fixed schedules (e.g. every Friday at 8pm), or after X many hours or days since the environment was last updated, or any combination thereof. This is particularly useful for ephemeral dev and PR preview environments, which can easily add up in costs over time.
Please see the Automatic Environment Cleanup guide for details on how it works and how to use it.
Requires Garden Cloud (any subscription tier)
Cloud Variables and Secrets
Another feature previously only available in Garden Enterprise, now available to all Garden Cloud users, and with more flexibility than previously. You can now define lists of variables and secrets in Garden Cloud and use them in your Garden projects. Each variable or secret can optionally be scoped to individual environment types or users. New in this release is the ability to use the same variables across multiple Garden projects (which has been requested by several users).
Please see the Remote Variables and Secrets guide for details on how to set this up and use it in your projects.
Requires Garden Cloud (any subscription tier)
Command history and activity in Garden Cloud
Also previously only available in Garden Enterprise, we now gather a history of executed commands along with detailed action results and logs, all neatly organized in the Garden Cloud UI.
You can opt out of this (and still use Garden Cloud for other things) by setting GARDEN_DISABLE_CLOUD_LOGS=1 in your shell environment or pipelines, or by adding disableCloudLogs: true to your Project configuration.
Requires Garden Cloud (any subscription tier)
Log output changes and improvements
Based on user feedback, we’ve decided to make the default log level for Garden commands verbose (instead of info). This means you’ll see more details by default when running CLI commands, such as container build logs, action execution logs etc.
To revert to the previous behavior, you can always set --log-level=info (or -l=2) in your Garden CLI commands or set GARDEN_LOG_LEVEL=info in your shell environment.
We’ve also added better progress output during execution along with a short summary at the end, to better identify which actions are running, pending, what failed, succeeded etc.
All changes
Features
- stream logs to Garden Cloud via gRPC (#7793) (0bd363e6a)
- api: make cloud util commands visible (#7742) (1b86d56f9)
- core: emit deploy run results to Garden Cloud (#7781) (a0870606b)
Improvements
- show verbose log output by default (#7799) (f5b042c08)
- aec: add more detail to env update events (#7830) (932ebff2d)
- cli: print graph status message on interval during solve (#7769) (a306d5f81)
- logs: print graph summary at end of graph solve (#7832) (3fd26a3d4)
- logs: misc log-related fixes and cleanup (#7809) (2bc471d5e)