1. Follow the procedure provided in the Documentation for installation of RHOSDS Operator. 2. At the initial stage Operator was getting installed successfully but the container in "devspaces" pod was not up due to which it was causing issue accessing the Dev Spaces dashboard. =============================   NAME READY STATUS RESTARTS AGE che-gateway-544c847b5f-2pwjg     4/4 Running 5 (150m ago) 26h devfile-registry-5b67fbfc4-ftptz    1/1 Running 0 149m devspaces-6cdb8889d4-6x8jk        0/1 Running 167 (5m22s ago) 2d1h devspaces-775ddb88b9-tgnd4      0/1 Running 66 (5m52s ago) 21h devspaces-dashboard-6f69fb55b4-ssxkj    1/1 Running 1 26h devspaces-operator-867df865d9-49b5q       1/1 Running 8 (150m ago) 26h devworkspace-controller-manager-6c758d4668-5fdsr    2/2 Running 94 (150m ago) 7d19h devworkspace-webhook-server-74859f9748-27p8w     2/2 Running 0 149m plugin-registry-57d979f7fd-sstkv    1/1 Running 0 148m postgres-66fd487fc8-88tjc      1/1 Running 4 6d1h ============================= 3. The Events showed "Readiness probe error" .  Updated client to change the timeout parameters which didn't work.  4. Again we went on call and tried the installation but this time the operator is not getting installed and subscription goes into "Pending" state.  5. Tried to clear old resources CRDs and reinstalled the operator still it didn't worked and the operator installation went into a "Pending" state.  6. As an alternate way we have tried to clear the resources and removed the operator using DSC tool from cli. After removal tried installation via CLI using dsc utility but that also didnt work.  Attached are the logs provided while trying installation using dsc utility.  Note: For more details Case summary is updated on case.