-
Spike
-
Resolution: Done
-
Blocker
-
None
-
None
-
5
-
False
-
None
-
False
-
Yes
-
https://gitlab.cee.redhat.com/service/managed-tenants/-/merge_requests/3418, https://gitlab.cee.redhat.com/service/managed-tenants/-/merge_requests/3420, https://gitlab.cee.redhat.com/service/managed-tenants/-/merge_requests/3424, https://github.com/integr8ly/integreatly-operator/pull/3009, https://github.com/integr8ly/integreatly-operator/pull/3016
-
RHOAM Sprint 32, RHOAM Sprint 33
What
add cro namespace to managed tenants and see if we can speed up the installation of sts addon. Currently we have to wait for the CRO ns to be created by integreatly-operator and then wait for hive to reconcile the sts-credentials secret.
How
enabling in managed-tenants is done like so https://gitlab.cee.redhat.com/service/managed-tenants/-/merge_requests/3092,
due to the sync selector set migration creation of an extra ns no longer works , once this is resolved we can proceed to test this spike
unknowns
STS specific
- will CRO be able to install in the namespace created by hive
- will hive wait for the addon to be removed before removing the cro ns
- will we be able to add finalizers to a hive created ns
- will uninstall work
Normal RHOAM install
- will upgrade from a cro ns created by integreatly to an addon using a hive created cro ns work
- will we have rbac to install in the cro ns subscriptions, installplans etc.
Done
answers to the above questions and follow up jira's to address the issues.
- blocks
-
MGDAPI-4936 Create CRO and 3scale NS in addon config for release
- Closed
- mentioned on
(2 mentioned on)