v0.4.0

[landscaper]

⚠️ Breaking Changes

• [USER] The landscaper-cli is removed from the landscaper repository. The cli will now be developed in a separate repository. (#80, @schrodit)
  • See https://github.com/gardener/landscapercli .
• [USER] The component-descriptor library has been updated which included a breaking change. The component-descriptor oci reference path construction has been updated to now use the following format <repocontext base url>/component-descriptor/<component name>:<component version> instead of the old <repocontext base url>/<component name>:<component version>. (#74, @schrodit)
• [DEVELOPER] The release tags from now are prefixed with v. (#76, @ialidzhikov)

✨ New Features

• [USER] An additional input value for the deploy executions has been added that contains information about the blueprint (#79, @schrodit)

🏃 Others

• [OPERATOR] category: bugfix (#83, @Nikolay-Neykov)
  • Fixing successful cleanup of resources of failed helm deployment
• [DEVELOPER] The oci client has been replaced with the centrally maintained client in https://github.com/gardener/component-cli/tree/main/ociclient. (#74, @schrodit)
• [DEVELOPER] The new oci client also includes a improved oci keyring which replaces the currently custom logic in the container deployer sync secret function. (#74, @schrodit)

0.3.0

[landscaper]

⚠️ Breaking Changes

• [USER] The blueprint resource type has been updated to landscaper.gardener.cloud/blueprint. The old type (blueprint) is still usable to keep backwards compatibility. (#59, @schrodit)
• [USER] The component-descriptor templating values and functions have changed (#59, @schrodit)
  • the resolved component descriptor (map of names) has been removed
  • component-descriptor access functions have been added for resources and component reference
  • list of all component references is available in the deployExecutor as components
  • For detailed information, see the blueprint documentation and the execution documentation.
• [OPERATOR] The registry config does now only use one registry configuration for all artifacts. The previous registry configuration for blueprints and components has been combined. (#59, @schrodit)
  • Adjust your landscaper configuration accordingly.

✨ New Features

• [DEVELOPER] The component descriptor oci resolve of the go-binding is integrated. Which caused a major refactoring of the registries in the landscaper: (#59, @schrodit)
  • the blueprint and artifact registry has been completely removed and are replaced by blob resolvers.
  • blueprint specific resolver is now part of the component registry and can resolve blueprints as artifacts.
  • the local blueprint resolver has been replaced with a CTF filesystem resolver. This now complies to the CNUDIE CTF specification (with a simplification that directories are automatically served as tar.gz).

🏃 Others

• [USER] The container deployer supports pulling OCI (blueprints, component descriptor, container images) artifacts from private registries by supplying respective auth credentials. (#69, @hendrikKahl)

0.2.0

[landscaper]

⚠️ Breaking Changes

• [USER] The component descriptor library has been updated to the latest version. ⚠️ note that the new version contains a breaking change: the localResources and externalResources have been merged into resources (#38, @schrodit)
• [USER] The resource kind selector in installations .spec.blueprint.ref.kind has been removed as there is no difference in the component descriptor resources anymore. (#38, @schrodit)
• [USER] The localResourcesand externalResourcs in the resource selector URI has been combined to only use resources now. (#38, @schrodit)

🏃 Others

• [OPERATOR] Added documentation for installation-component descriptor-Blueprint relation. (#57, @schrodit)
• [OPERATOR] Updated the base image for all controllers to gardenlinux 184.0 (#51, @schrodit)
• [OPERATOR] Added support to configure http fallback for oci registries that do not support https (#50, @schrodit)
• [OPERATOR] Added automated api-reference generation for Landscaper core resources (#49, @schrodit)
• [OPERATOR] Add check for cycles in deploy item template lists. (#33, @Diaphteiros)
• [OPERATOR] Added documentation for installations. (#32, @schrodit)
• [OPERATOR] It is now also possible to specify secrets and configmaps as source for data imports. (#30, @schrodit)
• [OPERATOR] A new manifest deployer version v1alpha2 has been introduced that allows the usage of policies per manifest. (#29, @schrodit)
• [OPERATOR] Adds a local command to the landscaper cli to locally render and verify blueprints. (#28, @schrodit)
• [OPERATOR] Added state handling for the templating executors (#23, @schrodit)
• [OPERATOR] Added validation for all landscaper resources (#18, @schrodit)

0.1.0

[landscaper]

Most notable changes

• [DEVELOPER] License and copyright information is specified in REUSE format. (#22, @msohn)

Improvements

• [OPERATOR] Added a manifest deployer to deploy raw kubernetes manifests. (#19, @schrodit)
• [OPERATOR] Added first simple nginx-ingress example (#17, @schrodit)

0.0.0

no release notes available