Uploaded image for project: 'OpenShift Top Level Product Strategy'
  1. OpenShift Top Level Product Strategy
  2. OCPPLAN-7768

Operator-SDK core project gets leaner

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • openshift-4.9
    • None
    • None
    • None
    • False
    • False
    • Not Set
    • No
    • Not Set
    • Not Set
    • Not Set
    • 0% To Do, 33% In Progress, 67% Done
    • Undefined

      Goal:

      Make Ansible and Helm Operator become individual libraries/projects, so users can import those libraries with their Golang Project.

      Benefits:

      • Better separation between Ansible/Helm/Golang so could have different project release paces.
      • Open the door for Hybrid Operator concept for helping mature the Operator capabilitiy level (Feature/OSDK-1134).

      Why is this important: 

      Ansible Operator and Helm Operator are historically glued in Golang codes in a single large SDK project. It's because under-the-hood they are tightly knit together (all are Go Operators), with the scaffolding and the rest SDK codebase.

      By splitting out helm/ansible repos + make go libraries for helm/ansible controllers, this paves the way for hybrid operator opportunities.

      Acceptance criteria:

      • splitting out helm/ansible repos
      • make go libraries for helm/ansible controller

      Related Work:

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

                Created:
                Updated: