Uploaded image for project: 'Operator Runtime'
  1. Operator Runtime
  2. OPRUN-2612 POC: Prototype a deppy implementation
  3. OPRUN-2614

Define a set of "known/supported" constraint definitions

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • False
    • None
    • False
    • OCPPLAN-9555 - Platform Operators
    • [OLM-220] Lacrimosa

      Goal: keep the scope small for the input API and implementation but defining a set of known/support constraint definitions, without surfacing the ability for users to define those definitions themselves (e.g. using CEL like in current OLM).

              tflannag@redhat.com Tim Flannagan (Inactive)
              tflannag@redhat.com Tim Flannagan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: