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

Custom semantic of namespace manifests

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • Strategic Product Work
    • False
    • False
    • OCPSTRAT-452 - OLM v1: Plain bundle format support

      Story: As an operator author I want to be able to leverage namespace manifests in my operator bundle to ensure that my operator is installed in a particular namespace with properties that I need to ensure, such as name or default node selectors when OLM applies the bundle.

      Acceptance criteria:

      • authors can include namespace manifests in the bundle
      • the namespaces manifest are applied first before any other resource
      • other manifests in the bundle can depend on the behavior above and reference the included namespace by name in other manifests

      Open questions:

      • what happens when no namespace manifest is included?
      • how does this namespace relate to the namespace in which the bundle is applied?

              Unassigned Unassigned
              DanielMesser Daniel Messer
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: