EPIC Goal

To make RHDH and other profiles work for any platform with no additional patching of default configuration.

Background/Feature Origin

There is an issue with filesystem permissions which does not allow to use the same default config for Openshift and K8s platfroms like EKS, AKS, GKE:
https://issues.redhat.com/browse/RHIDP-1560
So installation RHDH to these Platforms requires additional patching of deployment.yam, db-statefulset.yaml and service.yaml, as described:

• https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.4/html/installing_red_hat_developer_hub_on_google_kubernetes_engine/proc-rhdh-deploy-gke-operator.adoc_title-install-rhdh-gke#proc-rhdh-deploy-gke-operator.adoc_title-install-rhdh-gke. (#8)
• https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.4/html/installing_red_hat_developer_hub_on_amazon_elastic_kubernetes_service/proc-rhdh-deploy-eks-operator_title-install-rhdh-eks#installing-the-developer-hub-operator-with-the-olm-framework (#7)
• https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.4/html/installing_red_hat_developer_hub_on_amazon_elastic_kubernetes_service/proc-rhdh-deploy-eks-operator_title-install-rhdh-eks#installing-the-developer-hub-operator-with-the-olm-framework (#1)

Why is this important?

To improve user experience and avoid additional manual steps installing Operator.

User Scenarios

Operator installation as mentioned in the docs above

Acceptance Criteria

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>