Uploaded image for project: 'Hybrid Application Console'
  1. Hybrid Application Console
  2. HAC-50

SPIKE: OpenShift Console Operator vs New Operator

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • Milestone 1
    • None
    • Core
    • None
    • False
    • False
    • HAC Core Sprint 2, HAC Core Sprint 3, HAC Core Sprint 4

      Acceptance Criteria

      • Determine the ConsoleDot patterns around Operators
        • Backend services are different on CloudDot than frontend services
        • OpenShift Console Operator likely does not work due to other responsibilities it has, investigate further
          • Could a flag mitigate OpenShift Console features so we can just use it for HAC?
          • Release cadence for OCP may cause issues, think more on this
      • Look into what it would take to spin up a new Operator
        • Preference is in golang
        • Something to just deploy the OpenShift Console backend to get the bare bones going
        • We need something to deploy and health states for HAC backend

              bholifie Blake Holifield
              aballantyne Andrew Ballantyne
              Archiver:
              rhn-support-sthamilt Stacey Hamilton

                Created:
                Updated:
                Resolved:
                Archived: