-
Bug
-
Resolution: Duplicate
-
Blocker
-
None
-
3.2.0.GA
-
None
-
False
-
None
-
False
-
-
Description of problem:
Port exposure issues after migration from CRW 2.15 to Red Hat OpenShift Dev Spaces 3.2
Prerequisites :
OCP: 4.10 and above
Red Hat OpenShift Dev Spaces operator: v3.2.0
Steps to Reproduce:
1. Created sample workspace from the devspaces Dashboard using the default IDE.
2. Make sure the sample workspace created is up and running .
3. Open the workspaces dashboard and check accessing the workspace icon on the right-hand side loads the details of the IDE which has the URLs
Refer to screengrab [1] which clarifies the same.
Actual results:
The URL format is <devworkspace-server-subdomain>.<base-url>/<workspaceid>/<selected-editor>/<transilated-port> Instead of <routeID>-<namespace>.<base-url>/
Expected results:
The URL format should be : <routeID>-<namespace>.<base-url>/
Additional info :
1. Client has migrated from CRW 2.15 to Devspaces 3.2.
2. After the migration, existing workspaces came up with a button to convert. The conversion was successful and the workspaces came up and loaded successfully in IDE.
3. The problem is running of application inside the workspace that listens on a port.
Following is the update from the client in regard to this requirement and its impact :
This is causing issues with developers not getting access to the app. Is there a way to change the behavior of port rerouting to how it was working before?
Attachments:
devfile-in-crw2.15.yaml (checluster definition)
devfile-in-crw-3.2.yaml (Dev file generated after clicking the convert button)
checluster-codeready-workspaces.yaml (working dev file used in crw 2.15)