mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-07 00:48:01 +01:00
25 lines
1.9 KiB
Plaintext
25 lines
1.9 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * operators/understanding/olm/olm-understanding-dependency-resolution.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="olm-dependency-resolution-about_{context}"]
|
|
= About dependency resolution
|
|
|
|
Operator Lifecycle Manager (OLM) manages the dependency resolution and upgrade lifecycle of running Operators. In many ways, the problems OLM faces are similar to other system or language package managers, such as `yum` and `rpm`.
|
|
|
|
However, there is one constraint that similar systems do not generally have that OLM does: because Operators are always running, OLM attempts to ensure that you are never left with a set of Operators that do not work with each other.
|
|
|
|
As a result, OLM must never create the following scenarios:
|
|
|
|
- Install a set of Operators that require APIs that cannot be provided
|
|
- Update an Operator in a way that breaks another that depends upon it
|
|
|
|
This is made possible with two types of data:
|
|
|
|
[horizontal]
|
|
Properties:: Typed metadata about the Operator that constitutes the public interface for it in the dependency resolver. Examples include the group/version/kind (GVK) of the APIs provided by the Operator and the semantic version (semver) of the Operator.
|
|
Constraints or dependencies:: An Operator's requirements that should be satisfied by other Operators that might or might not have already been installed on the target cluster. These act as queries or filters over all available Operators and constrain the selection during dependency resolution and installation. Examples include requiring a specific API to be available on the cluster or expecting a particular Operator with a particular version to be installed.
|
|
|
|
OLM converts these properties and constraints into a system of Boolean formulas and passes them to a SAT solver, a program that establishes Boolean satisfiability, which does the work of determining what Operators should be installed.
|