Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessing public endpoints of workspace pod #22461

Closed
Deel96 opened this issue Aug 28, 2023 · 2 comments
Closed

Accessing public endpoints of workspace pod #22461

Deel96 opened this issue Aug 28, 2023 · 2 comments
Labels
kind/question Questions that haven't been identified as being feature requests or bugs. status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github.

Comments

@Deel96
Copy link

Deel96 commented Aug 28, 2023

Summary

In an older version of eclipse che the URL of the IDE looked something likes this:
https://192.168.49.2.nip.io/workspaced381305089e34ab0/theia-ide/3100

In a devfile it was possible to define public endpoints, which were acessible by following url
you define public endpoints which were acessible via following url:

https://<workspaceHash>-<number starting from 1>.<fqn>
e.g.:
https://workspaced381305089e34ab0-1.192.168.49.2.nip.io/ (1)

See this old issue:
#21634 (comment)

Now the workspace hash is not present anymore in the url, but can be obtained via kubectl
But I fail to access the exposed container like in the old version of che.

Do I have to do now something different with the current Che Version (7.72.0) ?

I also noticed that the public stack examples don`t have public endpoints anymore, only private ones.

I added the definition of my devfile below.

Relevant information

Che version 7.72.0

My devfile: https://gist.githubusercontent.com/Deel96/2fde413e707a73e6487464b16f6cafe3/raw/a6a08125f86a16b683cc02e4eebc07a431248f06/che-editor.yaml

@Deel96 Deel96 added the kind/question Questions that haven't been identified as being feature requests or bugs. label Aug 28, 2023
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 28, 2023
@Deel96 Deel96 changed the title Acessing public endpoints of workspace pod Accessing public endpoints of workspace pod Aug 28, 2023
@tolusha
Copy link
Contributor

tolusha commented Aug 28, 2023

The workspace URL has been changed.
You can find below the related issue:
#20598
eclipse-che/che-operator#1672

@Deel96
Copy link
Author

Deel96 commented Aug 28, 2023

Thank you for pointing me to the right direction!
To save the time for the next person asking the same question:

<username>-<project-name>-<endpointname>.<fqn>
worked for me.

@tolusha In the issue you meantioned points (.) are used instead of dashes (-).

You can also find the routes via the following kubectl command
kubectl get --all-namespaces ingress -o json 2> /dev/null| jq -r '.items[] | .spec.rules[] | .host as $host | .http.paths[] | ( $host + .path)' | sort | grep -v ^/

@Deel96 Deel96 closed this as completed Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Questions that haven't been identified as being feature requests or bugs. status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github.
Projects
None yet
Development

No branches or pull requests

3 participants