Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-1629

Transition Development from Helm-Chart Project to Operator Repository

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • orchestrator-operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      The current development process for the orchestrator chart for OCP is managed in the orchestrator-helm-chart repository. After development, the chart version is released to a hosted Helm repository. However, our primary release and installation mechanism is through a Helm-based operator located in the orchestrator-helm-operator repository.

      To release a new operator version, the charts must be manually copied from the Helm chart repository to the operator repository. This process is cumbersome and introduces unnecessary complexity.

      Moving the chart development directly into the operator repository would streamline the workflow, ensuring that chart versions are automatically aligned with operator versions.

      Tasks to be completed:

      1. Cease new updates to the OCP chart in the orchestrator-helm-chart repository.
      2. Transfer all documentation (READMEs and GitHub Pages) from the orchestrator-helm-chart repository to the operator repository.
      3. Relocate setup scripts from the orchestrator-helm-chart repository to the operator repository.
      4. Update any references in blogs and on the website to reflect this change.

              jgil@redhat.com Jordi Gil
              masayag@redhat.com Moti Asayag
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: