Uploaded image for project: 'Operator Runtime'
  1. Operator Runtime
  2. OPRUN-2280

Prototype Veneer api for declarative config

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • openshift-4.12
    • None
    • War Games [OLM 205], Xanadu [OLM 206], [OLM 212]Digimon, [OLM 213] Ectoplasm, [OLM 214] Florian, [OLM 217] Ivermectin
    • 0

      Create a prototype for a veneer layer on top of file based catalogs. As a result of this prototyping, come to a consensus on an enhancement proposal.

      There is an existing veneer prototype done by Joe, with a workflow implemented as part of OLM-2455.

      A simple veneer story: https://hackmd.io/J6PQYDnLTfqYGLWpOs44aQ
      Some previous work on semver: https://github.com/joelanford/declcfg/blob/main/internal/cmd/semver.go (the output is a semver channel)

      Things to think about for the final EP:

       - it should be easy for anyone to create their own
       - opm alpha veneer sub-command
       - how do we want distribute this? (opm alpha, or separate binary)
       - what can a veneer change over time? (what fields in an FBC are allowed to be changed by a veneer and what are the knock-on effects for something that's running on cluster)

       

      A/C:

       - convert https://github.com/joelanford/example-operator-index/ to Go
       - prototype level (no need for unit tests, etc.)

            rh-ee-jkeister Jordan Keister
            krizza@redhat.com Kevin Rizza
            Xia Zhao Xia Zhao
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: