-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
[Operator] On OCP, Automatically populate the baseUrls in the default app-config ConfigMap generated for each CR
-
M
-
False
-
-
False
-
To Do
-
RHIDP-4212 - Feature parity between Helm Chart and Operator
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
-
EPIC Goal
What are we trying to solve here?
Several issues reported since the docs restructuring in 1.4:
A common source of mistake/frustration is either misconfiguring the baseUrls. In the docs, it is not really clear that these information are mandatory for the Operator, when they configure their app-configs.
It would be great if the Operator could automatically populate this as a default app-config config map which is already generated. The user would still be able to customize these in their own custom app-config ConfigMap(s).
On OCP, the Operator could retrieve the ingress domain and automatically generate these baseUrls in the default app-config ConfigMap.
The baseUrl value would depend on the cluster Ingress domain and the `spec.application.route` parameters defined in the CR.
Background/Feature Origin
Why is this important?
User Scenarios
Dependencies (internal and external)
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>
