Deprecations

Deprecations

This document collects the features that have been deprecated in Garden 0.14.

Old configuration syntax

hotReload configuration field in modules

The 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 Code Synchronization Guide for details.

serviceResource.hotReloadArgs configuration field in kubernetes modules

The 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 Code Synchronization Guide for details.

spec.devMode configuration field in actions

The 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 actions

The 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 provider

The 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 type

The 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.

For the Run action kind see spec.manifestFiles and spec.manifestTemplates. For the Test action kind see spec.manifestFiles and spec.manifestTemplates.

spec.limits configuration field in container Deploy action

Please use the cpu and memory configuration fields instead.

Note! If the deprecated field spec.limits 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.

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.

See spec.cpu and spec.memory for the new syntax details.

limits configuration field in workflows

Please use the resources.limits configuration field instead.

Note! If the deprecated field limits 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.

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.

See resources.limits for the new syntax details.

Unsupported commands

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.

Deprecated configuration

podSelector configuration field in sync mode

The podSelector configuration field is deprecated and has no effect in spec.sync.overrides[].target and spec.sync.paths[].target configurations of kubernetes and helm Deploy actions. Please, use the combination of kind and name configuration fields instead.

Usage of the podSelector as a target sync resource can cause unpredicted behaviour, because such selector picks up the first matching Pod in the cluster. Instead, a pair of kind and name should be used with one of the following kinds: Deployment, DaemonSet or StatefulSet. Garden ensures that each kind of these resources has exactly 1 Pod when running in sync mode.

For kubernetes Deploy actions see spec.sync.overrides[].target and spec.sync.paths[].target. For helm Deploy actions see spec.sync.overrides[].target and spec.sync.paths[].target.

spec.ports[].hostPort configuration field in container Deploy action

It's generally not recommended to use the hostPort field of the V1ContainerPort spec. You can learn more about Kubernetes best practices at: https://kubernetes.io/docs/concepts/configuration/overview/