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

Codify the minimum set of expectations for operators to "work well" (not break) with OLM's ecosystem

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • [OLM 218] Jacaranda, [OLM-219] Koala, [OLM-220] Lacrimosa

      What makes for a well-behaved operator that works with OLM's current lifecycle ecosystem (e.g. packaging, update graphs, control logic idempotence, etc.).

      A/C:

       - Collect wisdom from SDK and PE
       -  Expectations defined
       - Update best-practices documentation for OLM
       - Docs reviewed by: PE, SDK, and DOCS

       

      Current best practices documentation:

      https://olm.operatorframework.io/docs/best-practices/common/

       

      E.g. If you need to change labels in a Deployment PodSpec between versions of the operator, you need to rename your deployment.

       

       

       

            Unassigned Unassigned
            njhale Nicholas Hale (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: