A service managing multi-tenant landscaper installations.
The Landscaper Service aims to implement a Kubernetes API extension, which provides and manages Landscaper installations as a service. Its goal is to install the Landscaper on configurable target Kubernetes clusters. Landscaper installations are isolated for each tenant, as each installation is hosted in its own virtual cluster (node-less Kubernetes cluster with its own Kube API server and etcd).
The documentation can be found here.
This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.
If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.
Copyright 2025 SAP SE or an SAP affiliate company and landscaper-service contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.
This repository is a fork of https://github.com/gardener/landscaper-service. The support for the Landscaper project is sunsetting in the Gardener organization. Maintainenance and development of the Landscaper project will continue in the https://github.com/openmcp-project/landscaper-service repository. This doesn't affect any feature or functionality of the Landscaper project. OCI images and OCM components can be consumed directly from within this repository GitHub Container Registry.