| title | sidebar_position |
|---|---|
Prerequisites |
1 |
-
For all examples, you need a running Landscaper instance.
-
A convenient tool we will often use in the following examples is the Landscaper CLI.
-
For building reusable components you require the OCM CLI.
-
During the following exercises, you might need to change files, provided with the examples. For this, you should simply clone this repository and do the required changes on your local files. You could also fork the repo and work on your fork.
-
In all examples, 3 Kubernetes clusters are involved:
- the Landscaper Host Cluster, on which the Landscaper runs
- the target cluster, on which the deployments will be done
- the Landscaper Resource Cluster, on which the various custom resources are stored. These custom resources are watched by the Landscaper, and define which deployments should happen on which target cluster.
It is possible that some or all of these clusters coincide, e.g. in the most simplistic approach, you have only one cluster. Such a "one-cluster-setup" is the easiest way to start working with the Landscaper.
The Guided Tour consists of several chapters, some of which build on each other. In order to get the most out of it, you should be following the Guided Tour in this sequence. If you have problems with the presentation of the Guided Tour, jump to the original github repository.
2. Upgrading the Hello World Example
4. Multiple Deployments in One Installation
5. Handling an Immediate Error
You can find a list of error messages and corresponding solutions here.
8. An Installation with an Externally Stored Blueprint
9. Helm Chart Resources in the Component Descriptor
14. Templating: Accessing Component Descriptors
15. Target Maps: Multiple Deploy Items
16. Target Maps: Target Map References
17. Target Maps: Multiple Subinstallations
18. Target Maps: Target Map on Subinstallation Level