v0.16.0

[landscaper]

📖 Documentation

• [USER] Changed description for deployment via OCI chart (gardener/landscaper#376, @JuergenMair)

🏃 Others

• [OPERATOR] Default context for component descriptor imports (gardener/landscaper#375, @achimweigel)
• [DEVELOPER] Add kubernetes utils to controller-utils module. (gardener/landscaper#374, @reshnm)

v0.15.2

no release notes available

v0.15.0

[landscaper]

✨ New Features

• [USER] It is now possible to configure a helm deploy item to automatically create the release namespace. (gardener/landscaper#370, @schrodit)
  • This behaviour is similar to Helm's --create-namespace flag.
  • The namespace creation can be configured by setting createNamespace: true.
  • For more details see the Helm deployer documentation.
• [USER] The continuous reconcile extension has been added to all current deployers. When enabled, the corresponding deploy items are reconciled with a fixed schedule, independently of any changes. Have a look at the deployer documentation for further information. (gardener/landscaper#341, @Diaphteiros)
• [OPERATOR] A GarbageCollector has been added to the Container Deployer to cleanup all resources that are once created by the container deployer. (gardener/landscaper#364, @schrodit)
  • It is now possible to delete deploy items (and manually remove their finalizer) without a need manually cleanup resources on the host cluster.

🐛 Bug Fixes

• [OPERATOR] Component Descriptors of deployers (helm, container, manifest) are fetched from default repository context if no other context is configured. (gardener/landscaper#367, @achimweigel)
• [OPERATOR] A bug in the UUID handling of resources in the Manifest and Helm Deployer has been fixed. (gardener/landscaper#352, @schrodit)

🏃 Others

• [OPERATOR] fix app version of sub helm charts (gardener/landscaper#354, @achimweigel)
• [DEVELOPER] New module "controller-utils" which may be used for custom controller development. (gardener/landscaper#366, @reshnm)

v0.14.2

no release notes available

v0.14.1

[landscaper]

🐛 Bug Fixes

• [OPERATOR] A bug in the UUID handling of resources in the Manifest and Helm Deployer has been fixed. (gardener/landscaper#352, @schrodit)

🏃 Others

• [OPERATOR] fix app version of sub helm charts (gardener/landscaper#354, @achimweigel)

v0.14.0

[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

• [DEPENDENCY] The controller-runtime has been updated to v0.10. (gardener/landscaper#322, @schrodit)
• [DEPENDENCY] The Kubernetes dependencies have been updated to v1.22. (gardener/landscaper#322, @schrodit)

v0.13.0

[landscaper]

⚠️ Breaking Changes

• [USER] The fields name and namespace in the config of a helm deploy item are now mandatory, since one or both of them being empty can lead to weird errors. (#308, @Diaphteiros)

✨ New Features

• [USER] Add new landscaper controller command line option "--landscaper-kubeconfig". (#306, @reshnm)
  • This option allows the landscaper controller to run inside a hosting cluster, but operate on landscaper resources in a different cluster.

🐛 Bug Fixes

• [USER] Fixed a bug regarding the defaulting of the container deployer which could cause it to generate invalid pod manifests. (#305, @Diaphteiros)

🏃 Others

• [OPERATOR] Support for compressed jsonschema definitions has been added (#299, @schrodit)
• [OPERATOR] Phase changes in deploy items are now properly propagated to their owning execution, even if the execution was already in a final phase and there weren't any changes to the installation. (#290, @Diaphteiros)
• [OPERATOR] Reconciliation of executions will now detect missing or outdated deployitems. (#290, @Diaphteiros)
• [OPERATOR] Phase changes in executions and subinstallations are now properly propagated to their owning installation, even if the installation was already in a final phase and there weren't any changes to the spec. (#281, @Diaphteiros)

Release v0.12.1

[landscaper]

🐛 Bug Fixes

• [USER] Fixed a bug regarding the defaulting of the container deployer which could cause it to generate invalid pod manifests. (#305, @Diaphteiros)
• [OPERATOR] Support for compressed jsonschema definitions has been added (#299, @schrodit)

v0.12.0

[landscaper]

⚠️ Breaking Changes

• [USER] The exportFromManifest attribute in the Helm ProviderConfiguration is now deprecated and replaced in the future. (#274, @schrodit)
  • Please use new combined exports from now on.

✨ New Features

• [USER] Add command line flags "webhook-url" and "certificates-namespace" which allow to run the webhooks server in an external cluster. (#279, @reshnm)
• [USER] It is now possible to specify exports from deployed manifests in the helm and manifest deployer. (#274, @schrodit)
  • See the dedicated export documentation for details.
• [USER] It is now possible to specify exports from referenced deployed manifests in the helm and manifest deployer. (#274, @schrodit)
  • With this it is possible for example to create a service account and export the token in the referenced secret.
• [USER] It is now possible to import component descriptors. See the documentation for blueprints and installations for more information. (#255, @Diaphteiros)
• [DEVELOPER] The kubernetes manifest handling of the manifest and helm deployer are combined and both deployers do now use the same apitypes and manifest handling. (#273, @schrodit)

🐛 Bug Fixes

• [USER] A bug has been fixed that caused target export from installation to not be consumable by other installations. (#288, @reshnm)
• [OPERATOR] The permissions for deployers have been fixed so that they are now allowed to create, update and patch events. (#294, @schrodit)
• [OPERATOR] A bug in the pull secrets sync of the container deployer has been fixed. (#294, @schrodit)
• [OPERATOR] It is now possible to provide oci images addressed by their digest in all landscaper provided helm charts. (#278, @schrodit)
• [OPERATOR] A syntax error in the landscaper agent helm chart has been fixed (951625f)
• [DEVELOPER] Landscaper is now able to parse json.RawMessage values that are null. (#284, @achimweigel)

🏃 Others

• [OPERATOR] The logging verbosity of reconciles has been adjusted to output more useful logs. (#294, @schrodit)
• [DEPENDENCY] The component-cli dependency has been updated to v0.29.0 (#291, @schrodit)

v0.11.2

[landscaper]

🐛 Bug Fixes

• [DEVELOPER] Landscaper is now able to parse json.RawMessage values that are null. (#284, @achimweigel)