Uploaded image for project: 'RHOS Request for Features'
  1. RHOS Request for Features
  2. RHOSRFE-84

To document RHOSO operators API schema

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • Documentation
    • None
    • Important
    • False
    • False
    • Hide

      None

      Show
      None

      I have decided to report this story after discussing customer's problem with some RHOSO engineers: after one of the changes was implemented, API schema was changed and this broken GitOps setup.

      In series of internal conversation there was an agreement that operators' API changes within same RHOSO release should only occur in critical circumstances. If they are implemented, they should be reflected in some release notes/changelog.

      There was an idea to create a documentation similar to https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/api_overview/index .

      I am reporting this story to ask engineering to discuss this problem and figure out possible solution. Please take a look at attached SDFC case and linked Jira issue to understand the context.

              kgilliga@redhat.com Katie Gilligan
              rhn-support-astupnik Alex Stupnikov
              rhos-conplat-core-operators
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: