Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-152 Parodos operator
  3. FLPATH-524

Automate operator deployment

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • parodos-backend
    • False
    • Hide

      None

      Show
      None
    • False
    • FLPATH 4, FLPATH 5, FLPATH 6, FLPATH 7

      As the parodos operator is fully generated via make target, a CI could be interesting to automate the creation and deployment of new versions of the operator

      It should be correctly tested before being pushed to quay and OperatorHub

            rh-ee-gfarache Gabriel Farache
            rh-ee-gfarache Gabriel Farache
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: