0.12.36
.0.12.35
, Garden Cloud now supports an additional Cleanup mode when using Automatic Environment Cleanup: Pause mode.Deployments
and StatefulSets
replicas to 0
, as opposed to deleting all the namespaces in the environment that is being cleaned up.kube-state-metrics
deployment changed. Please delete the kube-state-metrics
deployment, before upgrading in the kots admin console by running:kube-state-metrics
deployment will be re-created with the new label selectors, when you deploy Garden Enterprise 1.18.5 via the kots admin console.7.16.1
in order to mitigate against Log4Shell (only relevant for Enteprise customers who choose to install the additional monitoring services).Note: in future releases, we will enforce the usage of service accounts for automatic cleanups: meaning you will need to create a service account and assign it to the environment that will be automatically cleaned up.
>0.12.27
, a new tab called "Stack" will appear on the Namespace page.0.12.27
. Please rely on the new Stack tab for getting Services and Test statuses.kaniko
builds).Note that this functionality is currently only available for GitHub users. GitLab users can however still do bulk imports via the CLI (see note above).
Read-only
and save your changes:deploy-preview-env
and full-test-ci
workflows.baseBranches
filter on workflow configs. This is useful for running workflows on merges to your main branch, or any other base branch for that matter. Here's an example where we run a given workflow every time a pull/merge request is merged (not just closed), and the base branch is main
: