Commodore-managed inventory parameters
This page provides a reference for all inventory parameters which are injected into the hierarchy by Commodore.
The parameters are injected using the class
This class is created by Commodore in file
The class is included in each Kapitan target with the lowest precedence of all classes.
cluster holds the following information about the cluster and its tenant:
The cluster’s ID (the name of the cluster object managed by Lieutenant).
The cluster’s display name.
The ID of the cluster’s tenant.
The display name of the cluster’s tenant.
The cluster catalog Git repository URL.
The cluster’s static facts, as stored in the cluster’s Lieutenant object.
The following facts are mandatory:
The cloud provider on which the cluster is installed.
The cloud region on which the cluster is installed. Mandatory only for clouds which have multiple regions.
The Kubernetes distribution of the cluster.
The cluster’s dynamic facts as reported by Steward on the cluster.
There are currently no mandatory dynamic facts.
Components shouldn’t directly consume dynamic facts. Instead, components should expose a parameter which can be configured with a dynamic fact if information from dynamic facts should be used in a component. This minimizes the coupling between components and the presence of dynamic facts, and allows components to degrade gracefully when a dynamic fact is missing for a Project Syn installation.
This could look something like
Project Syn global configuration repository
Commodore adds some "meta-parameters" to each component’s Kapitan target. These are provided to simplify component configurations.
Commodore provides the following component-specific top-level parameters
This parameter provides the absolute path to the component’s base directory.
This parameter is intended for component authors to use in
kapitan.dependencies entries when referencing files in the component directory.
This parameter provides the absolute path to the Kustomize wrapper script bundled with Commodore. This parameter is intended for component authors to use to call Kustomize in components. See the Kustomization best practices for more details.