Skip to content

v0.14.0
Compare
Choose a tag to compare
@gardener-robot-ci-1 gardener-robot-ci-1 released this 20 Oct 10:29
· 1263 commits to master since this release
v0.14.0
27a04da

[landscaper]

⚠️ Breaking Changes

  • [USER] The helm version has been updated to 3.7 which includes a breaking change in the OCI Artifact structure of helm charts. (gardener/landscaper#343, @schrodit)
    • The Landscaper helm deployer is still able to work with both versions.
    • Please update your helm charts to ensure that they keep working in the future!
  • [USER] Imports of component descriptor lists now provide the data of a real component descriptor list and not only the contained components (gardener/landscaper#340, @achimweigel)
  • [USER] Exports that are not defined by the blueprint are now removed from the templating result. (gardener/landscaper#319, @schrodit)
    • Be aware that this might break blueprint that export data which is not defined.
  • [USER] The landscaper helm chart has been separated into two helm subcharts. (gardener/landscaper#313, @reshnm)
    • This was done to make the creation of the landscaper RBAC components re-usable.
    • When using the helm chart, all values that previously have been passed directly to the landscaper helm chart,
    • now have to be put into an additional landscaper object.
    • For example:
    • landscaper:
    • registryConfig: {}
    • now becomes
    • landscaper:
    • landscaper:
    • registryConfig: {}
    • Service account settings are now specified at a global level.
    • For example:
    • global:
    • serviceAccount:
    • controller:
    • create: true
    • name: landscaper-controller
  • [OPERATOR] The published Landscaper helm charts are now created with helm version 3.7 which includes a breaking change in the OCI Artifact structure of helm charts. (gardener/landscaper#343, @schrodit)
    • Update your local Helm Cli to 3.7+ in order to install the Landscaper or the Deployers.
  • [DEVELOPER] Extension hooks have been introduced to enable deployers to extend and modify the deployer library's default reconciliation flow. The Deployer interface has been expanded and its implementations now need an additional ExtensionHooks() method. Check out the documentation here. (gardener/landscaper#292, @Diaphteiros)

✨ New Features

  • [USER] The Landscaper now also validates target imports and waits until Installations that have created that target are finished. (gardener/landscaper#344, @schrodit)
  • [USER] It is now possible to define namespaced context object that contain previous global configuration like the repository context or registry pull secrets. (gardener/landscaper#334, @schrodit)
    • It enables the Landscaper to handle multiple tenants separated by namespace.
    • The Context feature is backwards-compatible so all installations should work as before.
    • This backwards-compatibility is archived by deploying a default context in each namespace that is automatically referenced by installations.
    • See the Context and Installation documentation for more details.
  • [OPERATOR] Adds a new index method for the blueprint store that uses the digest of the blueprints has been added and made as default. (gardener/landscaper#342, @schrodit)
    • With that change blueprints are updated when the content of a blueprint changes which is useful for development.
  • [OPERATOR] The Landscaper Configuration does now expose some controller specific configuration to fine tune the controllers. (gardener/landscaper#335, @schrodit)
    • See the Landscaper Configuration example for more details.
  • [DEVELOPER] A deployer library extension which enables continuous reconciliation of deploy items has been implemented. See here for the documentation. (gardener/landscaper#331, @Diaphteiros)

🐛 Bug Fixes

  • [USER] A bug in the import validation has been fixed that caused the Landscaper to panic when a root Installation is validated. (gardener/landscaper#344, @schrodit)
  • [USER] Adds dependencies between kubernetes resources in the helm and manifest deployer so resources can be deployed that requires other resources. (gardener/landscaper#321, @schrodit)
    • For example namespaces are now deployed before any other namespaced resources.
  • [USER] A bug has been fixed that caused the installation to stuck in deletion if the installation is erroneous. (gardener/landscaper#317, @schrodit)
    • Updated configuration is now correctly propagated during deletion and it is possible to set the force-reconcile annotation.
    • Installations that never had a successful execution (never have deployed an execution nor an installation) are now directly deleted.
  • [OPERATOR] Installations which contain neither an execution nor subinstallations will now be set to Succeeded (if the imports are fulfilled) instead of being stuck without a phase. (gardener/landscaper#326, @Diaphteiros)

🏃 Others

Assets 8
Loading