-
Epic
-
Resolution: Done
-
Critical
-
None
-
Compound Constraints
-
False
-
False
-
Done
-
0% To Do, 0% In Progress, 100% Done
-
L
Story: As a operator developer / OLM package maintainer I need to be able to express complex, compound constraints on my operator bundle so that it pulls the specific dependency that I need and leads to unambiguous dependency resolution when my operator is installed on cluster.
Acceptance criteria:
- the dependency specific of OLM bundles allows to express grouped / compound constraints to create arbitrary combinations of properties that dependencies have to satisfy