Deprecations
Last updated
Was this helpful?
Last updated
Was this helpful?
This document collects the features that have been deprecated in Garden 0.14.
hotReload
configuration field in modulesThe module-level hotReload
configuration field was removed in Garden 0.13 and has no effect. Please use actions with the sync
mode instead.
See the for details.
serviceResource.hotReloadArgs
configuration field in kubernetes
modulesThe serviceResource.hotReload
configuration field in kubernetes
modules was removed in Garden 0.13 and has no effect. Please use actions with the sync
mode instead.
See the for details.
spec.devMode
configuration field in actionsThe spec.devMode
configuration field in actions is deprecated in Garden 0.14. Please use spec.sync
configuration field instead.
The old fields spec.devMode
are automatically converted to spec.sync
in Garden 0.14 when using apiVersion: garden.io/v2
in the project-level configuration.
spec.localMode
configuration field in helm
, kubernetes
and container
Deploy actionsThe local-mode feature was completely removed in 0.14, and the spec.localMode
configuration syntax has no effect. Please remove all spec.localMode
entries from your configuration files.
resources.sync
config field in the kubernetes
providerThe resources.sync
config field in the kubernetes
provider has no effect in Garden 0.13 and 0.14., Please remove it from your kubernetes
provider configuration.
The resources.sync
config field in the kubernetes
provider was only used for the cluster-docker
build mode, which was removed in Garden 0.13.",
spec.files
configuration field in kubernetes-pod
action typeThe spec.files
configuration field in kubernetes-pod
action type has no effect. Please remove it and use spec.manifestFiles
or spec.manifestTemplates
instead.
See the reference documentation for details.
spec.limits
configuration field in container
Deploy actionPlease use the cpu
and memory
configuration fields instead.
Please do not use both spec.limits
and spec.cpu
and/or spec.memory
simultaneously,
and use only the latter pair of fields. Otherwise, the values from the old field spec.limits
will be used.
limits
configuration field in workflowsPlease use the resources.limits
configuration field instead.
Please do not use both limits
and resources.limits
simultaneously,
and use only resources.limits
. Otherwise, the values from the old field limits
will be used.
cleanup-cluster-registry
The cleanup-cluster-registry
command in the kubernetes
and local-kubernetes
plugins is not supported in Garden 0.14. This command no longer has any effect as of version 0.13! Please remove this from any pipelines running it.
For the Run
action kind see and .
For the Test
action kind see and .
Note! If the deprecated field
is defined in the container
Deploy action config,
Garden 0.14 automatically copies the field's contents to the spec.cpu
and spec.memory
,
even if the latter are defined explicitly.
See and for the new syntax details.
Note! If the deprecated field is defined in the workflow config,
Garden 0.14 automatically copies the field's contents to the resources.limits
,
even if the latter is defined explicitly.
See for the new syntax details.