Landscaper provides the means to describe, install and maintain cloud-native landscapes. It allows you to express an order of building blocks, connect output with input data and ultimately, bring your landscape to live.
What does a 'landscape' consist of? In this context it refers not only to application bundles but also includes infrastructure components in public, private and hybrid environments.
While tools like Terraform, Helm or native Kubernetes resources work well in their specific problem space, it has been a manual task to connect them so far. Landscaper solves this specific problem and offers a fully-automated installation flow. To do so, it translates blueprints of components into actionable items and employs well-known tools like Helm or Terraform to deploy them. In turn the produced output can be used as input and trigger for a subsequent step - regardless of the tools used underneath. Since implemented as a set of Kubernetes operators, Landscaper uses the concept of reconciliation to enforce a desired state, which also allows for updates to be rolled out smoothly.
- The documentation can be found here or you jump directly to the Guided Tour.
- A list of available deployers is maintained here.
- A glossary can be found here
- Installation instructions can be found here
This repository is a fork of https://github.com/gardener/landscaper. 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 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.