Uploaded image for project: 'Operator Ecosystem'
  1. Operator Ecosystem
  2. OPECO-2755

Bootstrap repo under operator-framework org

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • Strategic Product Work
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • OPECO 234

      Goal: 

      The goal of this ticket is to bootstrap the v1 CatalogSource repository under the operator-framework org. 

       

      Previous work: 

      https://github.com/anik120/rukpak-packageserver contains a significant chunk of the prototyping done as part of OPECO-2639.

       

      Open question: 

      Are we comfortable just transferring the repository to the operator-framework org, since a lot of work has already gone into that? That would only entail renaming the project to a more suitable name, and transfer of ownership thereafter. 

       

      Note: The images used in the prototype repo are stored in a private namespace in an image registry (docker.io/anik120). The images need to be move to the image registry being used for other OLM v1 projects. 

      AC: 

      • A repository exists under operator-framework org, that is the v1 CatalogSource repository.
        • operator-framework/catalog-server?
      • A code owner file exists in the repository 
      • New upstream catalog/something-dev channel in k8s slack

              anik120 Anik Bhattacharjee
              anik120 Anik Bhattacharjee
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: