v0.20.0

no release notes available

v0.19.0

[landscaper]

✨ New Features

• [OPERATOR] The context reference is not properly passed to all DeployItems and subinstallations. (gardener/landscaper#392, @reshnm)
  • With that the deployers are now able to use the secrets defined in the Context to access remote artifacts.
  • This is especially useful for multi-tenant scenarios where everything should be isolated by the namespace.

🐛 Bug Fixes

• [OPERATOR] Cyclic references in jsonschema files are now detected and cause a corresponding error instead of getting the landscaper stuck in endless recursion. (gardener/landscaper#393, @Diaphteiros)

v0.18.0

[landscaper]

🐛 Bug Fixes

• [USER] The helm deployer will now deploy CRDs in the crds folder of a chart (see here) instead of ignoring them. (gardener/landscaper#389, @Diaphteiros)
• [USER] Fixed a bug in the helm deployer which prevented it from deploying charts that contain CRDs together with corresponding resources. (gardener/landscaper#389, @Diaphteiros)
• [USER] Resolving nested jsonschema references across components now works as intended. (gardener/landscaper#388, @Diaphteiros)
• [USER] Add namespace read permissions to the landscaper controller clusterrole in the landscper rbac chart. (gardener/landscaper#387, @reshnm)

🏃 Others

• [DEVELOPER] ⚠️ Another dependency for testing has been added, please re-run make install-requirements before running make test. (gardener/landscaper#388, @Diaphteiros)

v0.17.0

[landscaper]

🏃 Others

• [OPERATOR] Fix responsibility settings of the deployer in a multi environment setup of the landscaper (gardener/landscaper#383, @achimweigel)

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)