Releases: gardener/landscaper
Releases · gardener/landscaper
v0.7.0
[landscaper]
✨ New Features
- [USER] DeployItem's type is now immutable and cannot be updated. (#144, @schrodit)
- [USER] Helm charts and execution containers can be fetched from private OCI registries with the credentials provided as
Installation.spec.registryPullSecrets
(#130, @loewenstein) - [OPERATOR] The validation webhook and the landscaper controller are now split into different containers and deployment. (#146, @schrodit)
- This is done to ensure isolation of validation and the actual load in the controller.
- Checkout the updated landscaper helm chart.
- [OPERATOR] All deployers can now be installed using the offically created blueprints (#126, @schrodit)
🐛 Bug Fixes
- [USER] Fixed a bug in the Landscaper controller that caused a panic when a imported configmap key was undefined. (#145, @schrodit)
- [USER] A bug has been fixed that caused the provider status of a manifest deploy item to grow infinite when the resource could not be created. (#129, @schrodit)
🏃 Others
v0.6.2
no release notes available
v0.6.1
v0.6.0
[landscaper]
✨ New Features
- [USER] It is now possible to omit the namespace from configmap or secret refs. The namespace is now defaultet to the installation's namespace. (#114, @schrodit)
- [OPERATOR] It is now possible to overwrite deployer configuration when the deployer is part of the landscaper controller. (#121, @schrodit)
- [OPERATOR] The landscaper-controller will now automatically deploy the CRDs for its resources upon startup. (#101, @MrBatschner)
- [OPERATOR] Add a webhook that validates
Installation
,Execution
, andDeployItem
resources. (#64, @Diaphteiros) - [DEVELOPER] The go version has been updated to 1.16.0 (0480f13)
🐛 Bug Fixes
- [USER] A bug has been fixed that causes the landscaper and all deployers to not respect docker-config files. (#122, @schrodit)
- [USER] Several bugs in the container deployer have been fixed that caused the container to not correctly write exports or restore the state. (#121, @schrodit)
- [USER] A bug has been fixed that caused the import validation to stuck when a non-dataref import has been defined on a dependent installation. (#117, @schrodit)
- [USER] The landscaper non-CRD resource jsonschemes are now generated using the Kubernetes OpenAPI-Library. (#109, @schrodit)
- This fixes several issues with the current jsonschemas.
- [OPERATOR] [Manifest Deployer] A bug in the manifest deployer has been fixed that causes it to not properly write its state in case of errors during the apply. (#119, @schrodit)
- [DEVELOPER] A bug has been fixed that prevented usage of the apis module with the landscaper (32af92c)
- [DEPENDENCY] The kubernetes versions are pinned to v1.19.7 to fix a bug in the code-generator in k8s v1.20: kubernetes/kubernetes#98380 (#113, @schrodit)
📖 Documentation
- [USER] A new tutorial and documentation about the usage of external jsonschemas has been added. (#114, @schrodit)
🏃 Others
- [OPERATOR] Expose controller-runtime metrics for landscaper-controller and add oci cache metrics. (#110, @hendrikKahl)
- [OPERATOR] Landscaper's Deployers can now be deployed from their very own Helm charts. (#107, @MrBatschner)
- [DEVELOPER] A integration test for the simple-import and aggregation tutorial has been added. (#117, @schrodit)
- [DEVELOPER] A integration test framework has been added that make it possible to run tests against a cluster with a running landscaper. (#99, @schrodit)
- [DEVELOPER] A integration test has been added that tests the simple nginx-ingress tutorial. (#99, @schrodit)
- [DEPENDENCY] Update controller-runtime dependency to
v0.8.1
(#100, @Diaphteiros) - [DEPENDENCY] The component-cli has been updated to v0.8.0 (51bcd7c)
- [DEPENDENCY] The component-spec has been updated to v0.0.31, which fixes a bug in the component descriptor oci reference generation. (51bcd7c)
v0.5.3
[landscaper]
🐛 Bug Fixes
- [USER] A bug has been fixed that caused the Landscaper to not properly write the state in secrets. (0fc9cd5)
🏃 Others
v0.5.2
no release notes available
v0.5.1
v0.5.0
[landscaper]
⚠️ Breaking Changes
- [USER] Add support for inline component descriptors. (#93, @hendrikKahl)
- installation.spec has a new componentDescriptor field containing either an inline component descriptor or a reference.
- Accordingly, installation.spec.blueprint.ref was changed: To reference the blueprint resource within a component descriptor, only a resourceName is needed where previously also the component descriptor was referenced.
- [DEVELOPER] A separate module has been created for the landscaper api objects. Get the api by running
go get github.com/gardener/landscaper/apis
(#95, @schrodit)
✨ New Features
- [USER] A new template function has been added to get the effective repository context for a component descriptor (#92, @schrodit)
- [USER] [Helm Deployer] It is now possible for specify the helm chart that is deployed by the helm deployer deployer either (#82, @schrodit)
- with a oci artifact ref
- as base64 encoded gzip archive
- from a remote url
- or from a component descriptor resource of type
helm
orhelm.io/chart
(preferred)
🐛 Bug Fixes
- [USER] A bug has been fixed that caused a valid yaml rendered by a helm chart to be treated as kubernetes manifest. (#91, @schrodit)
- This caused and issue when this resource was try to be created as kubernetes resource.
- [USER] A bug has been fixed that prevented a installation with a optional input to succeed when the import was not provided. (5cb089d)
- [USER] A bug has been fixed that caused the init container to panic if no pull secrets are defined (7b244cf)
📖 Documentation
- [USER] A new tutorial has been added that describes the usage and development of local artifacts. (#92, @schrodit)
🏃 Others
- [DEVELOPER] The component-cli has been updated to v0.6.0 and the component-spec has been updated to v0.0.30 (bdd97d5)