-
Story
-
Resolution: Done
-
Normal
-
None
-
2
-
False
-
None
-
False
-
Yes
-
-
-
-
-
-
1.17.0-9
-
No
-
Removes any instances of the Cloud Resource Operator deployment and Postgres customResources that are still present after the migration and removal of JupyterHub from RHODS
-
No
-
Pending
-
None
-
RHODS 1.17
As part of migrating from jupyterhub to notebook controller we have a lot of migration specific code in deployer as well as some floating objects in OpenShift. We should get rid of these remaining objects in 1.17
- Enable deletion of CRO objects in deployer (there is commented out code already)
- Remove yq binary from deployer repo (and update corresponding dockerfiles)
- Remove all migration specific code except anything that is required specifically for CRO cleanup.
- This means we will have a follow-ontask in 1.18 to get rid of migration code that's specific to CRO
- Ensure that `odh-enabled-applications-config` has the right flags set. We've noticed in 1.15->1.16 testing that both jupyterhub and jupyter are set to enabled. This is possibly an odh-dashboard bug, so confirm with odh-dashboard developers one way or the other.
- duplicates
-
RHODS-5069 CRO components are not getting deleted after the KFNBC migration
- Closed
- links to
- mentioned on