Skip to content

Releases: gardener/landscaper

v0.46.0

20 Feb 14:57
Compare
Choose a tag to compare

[landscaper]

🏃 Others

v0.45.0

26 Jan 13:38
Compare
Choose a tag to compare

[landscaper]

✨ New Features

v0.44.0

20 Jan 10:59
Compare
Choose a tag to compare

[landscaper]

✨ New Features

🏃 Others

v0.43.0

04 Jan 09:32
Compare
Choose a tag to compare

[landscaper]

✨ New Features

🐛 Bug Fixes

📖 Documentation

🏃 Others

v0.42.0

22 Nov 09:45
Compare
Choose a tag to compare

[landscaper]

🏃 Others

  • [OPERATOR] Revert the replacement of the virtual-garden component with shoot clusters in the landscaper-service component. (gardener/landscaper#639, @reshnm)

v0.41.0

21 Nov 11:52
Compare
Choose a tag to compare

[landscaper]

✨ New Features

v0.40.0

16 Nov 10:41
Compare
Choose a tag to compare

[landscaper]

⚠️ Breaking Changes

  • [USER] Target's Spec.SecretRef field now is of type *LocalSecretReference (instead of SecretReference). This means that a secret reference in a target may not contain a Namespace anymore, only Name and optionally Key are allowed. (gardener/landscaper#629, @Diaphteiros)
  • [USER] Referencing a kubeconfig secret in a Target of type landscaper.gardener.cloud/kubernetes-cluster by specifying kubeconfig.secretRef is now deprecated and will be removed in the future. Use the Target's spec.secretRef field instead. (gardener/landscaper#629, @Diaphteiros)
  • [DEVELOPER] The definitions for Target types have moved from apis/core/v1alpha1 to apis/core/v1alpha1/targettypes. (gardener/landscaper#629, @Diaphteiros)
  • [DEVELOPER] The deployer library now resolves secret references in Targets (only those referenced in Spec.Target of the deployitem) before calling the deployer-specific functions. Instead of providing a Target to these functions, it now gives a ResolvedTarget as argument. This is a new type, consisting of the original Target as well as a Content field, which contains the actual content of the Target - either its inline configuration or the result of the resolved reference. (gardener/landscaper#629, @Diaphteiros)
  • [DEVELOPER] Target's Spec.Configuration field now is of type *AnyJSON (instead of AnyJSON). It is expected to be nil, when Spec.SecretRef is set. (gardener/landscaper#629, @Diaphteiros)

✨ New Features

  • [USER] The resolved Target referenced at .spec.target in a container deployitem is now available within the container. The TARGET_PATH env variable points to a json file containing the original Target (under target) as well as its resolved content (under content). See the updated documentation. (gardener/landscaper#629, @Diaphteiros)
  • [OPERATOR] The Landscaper webhook now validates that at most one of Configuration and SecretRef in a Target's Spec is set, not both. It is possible to create empty Targets with neither field being set. (gardener/landscaper#629, @Diaphteiros)

🐛 Bug Fixes

  • [OPERATOR] Fixed a bug which caused the cyclic dependency check for subinstallations to sometimes contain the wrong cycle in the error message. (gardener/landscaper#636, @Diaphteiros)

🏃 Others

v0.39.0

28 Oct 14:56
Compare
Choose a tag to compare

[landscaper]

⚠️ Breaking Changes

  • [USER] The ComponentOverwrites custom resource has been removed and is replaced by the new ComponentVersionOverwrites custom resource, which is namespace-scoped. If you upgrade from an existing Landscaper installation, you have to migrate all ComponentOverwrites resources to the new format and delete the ComponentOverwrites CRD afterwards. See the documentation for further information. (gardener/landscaper#430, @Diaphteiros)

✨ New Features

🐛 Bug Fixes

🏃 Others

v0.38.0

13 Oct 10:52
Compare
Choose a tag to compare

[landscaper]

🏃 Others

v0.37.0

06 Oct 12:22
Compare
Choose a tag to compare

no release notes available