Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-2387

[Tech Debt] Multiple RHDH bundles, which makes it confusing and error-prone to maintain

Create Doc EPIC for Fe...Prepare for Y ReleasePrepare for Z ReleaseXMLWordPrintable

    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • Release Note Not Required
    • RHDH Install 3265, RHDH Install 3266, RHDH Install 3267, RHDH Install 3268

      [2307874481] Upstream Reporter: Armel Soro
      Upstream issue status: Open
      Upstream description:

      /kind user-story /priority low

      User Story

      As an operator developer, I want to have the RHDH bundle manifest generated So that I can simplify the maintenance of this CSV and reduce the potential errors caused by an out-of-sync downstream bundle (especially regarding the operator permissions, as caught for example in #360 and #351).

      Kustomize could be a great fit for this, but any better solution is also welcome.

      Similar to the make bundle command which generates the CSV for the upstream operator (which is version-controlled for review), we could imagine a make bundle-rhdh that would generate the CSV for RHDH off of this upstream CSV using Kustomize overlays/patches. It will still need to be version-controlled for review in .rhdh/bundle.

      `make bundle PROFILE=rhdh` could be leveraged to generate the expected bundle under `bundle/rhdh`. Any further customizations should be really minimal.

      Acceptance Criteria

      • make bundle or `make bundle PROFILE=rhdh` should generate the expected rhdh bundle under bundle/rhdh
      • It should put as many specifics under the Kustomize manifests/overlays
      • If specific things need to be done but are not supported by Kustomize, we should do that using basic scripting in the Makefile
      • It should remove the .rhdh/bundle/manifests folder
      • Downstream pipelines should be updated accordingly and should continue to work as previously
      • It should not result in breaking changes in the way the operator is installed/upgraded
      • It should update CI to auto-push the resulting downstream bundle, similar to what we are doing for the upstream bundle - see https://github.com/janus-idp/operator/blob/main/.github/workflows/pr-bundle-diff-checks.yaml#L63-L99

      Context


      Do you have an idea what prevents us to auto generate the CSV file for downstream instead?

      Originally posted by @gazarenkov in https://github.com/janus-idp/operator/pull/361#discussion_r1603045859

      Upstream URL: https://github.com/janus-idp/operator/issues/362

       

              rh-ee-asoro Armel Soro
              rh-ee-asoro Armel Soro
              RHIDP - Install
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: