The Landscaper CLI supports users to develop, maintain, and test components processed by the Landscaper. This comprises the handling of objects like component descriptors, blueprints, installations, etc.
The Landscaper CLI integrates the commands of the Components CLI.
The Landscaper CLI adds commands for the following use cases:
- Automatic setup of a landscaper and an OCI registry for development
- Development of components including a component descriptor and blueprint
- Local validation of such components
- Support for testing components on a kubernetes cluster
- Support for accessing and maintaining components with a blueprint in OCI registry
Remark: This version of the Landscaper CLI requires that you have installed helm version 3.7 or higher due to some fundamental API changes especially with respect to the handling of helm charts stored as OCI resources.
Installation instructions can be found here.
Detailed descriptions for commands could be found here.
The command reference is located here.
The Landscaper CLI support the installation of the Docker OCI registry with the quickstart command.
A description how to access an OCI registry which requires authentication with the Landscaper CLI can be found here.
Other examples: https://github.com/gardener/landscaper/blob/master/docs/tutorials/02-simple-import.md