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

[UPSTREAM] rfc: olmv1 kubectl-operator package discovery #2208

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Future Sustainability
    • False
    • Hide

      None

      Show
      None
    • False
    • 3
    • None
    • None
    • Quagsire Sprint 277, Rhydon Sprint 278

      A/C:

      • Detail minimal search API to list contents of all catalogs in cluster.
      • Evaluate methods of exposing the catalogd search API off cluster. (port-forwarding, nodeport, gateway)

      Background:
      The kubectl-operator v1 subcommands do not have a subcommand to search catalog contents currently. The simplest implementation of this command involves:

      • accessing catalog contents
      • querying available catalogs for their entire contents, dumping returned bundles and associated metadata as parseable json/yaml.

      To access catalog contents, the catalog needs to be queried directly via the on-cluster catalogd service by either:

      • port-forwarding (Note: portforwarding connection can fail/timeout when transmitting large catalogs)
      • setting up a gateway
      • exposing the catalogd service via a nodeport.

      An RFC for the minimal search API for package discovery will detail these different approaches and any relevant alternative means to implementing a way of listing all contents of every catalog in a cluster.

              Unassigned Unassigned
              ankithom Ankita Thomas
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: