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

There is no CHE_DASHBOARD_URL or PLUGIN_REGISTRY_URL in the dev container #21102

Closed
benoitf opened this issue Feb 1, 2022 · 1 comment · Fixed by eclipse-che/che-dashboard#481
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system. sprint/current

Comments

@benoitf
Copy link
Contributor

benoitf commented Feb 1, 2022

Describe the bug

it seems that dashboard is only adding the URLs links to the editor devWorkspaceTemplate but not to all containers

Che version

next (development version)

Steps to reproduce

Open a terminal in a container that is not the editor container
check that *_URL env variables are not defined

Expected behavior

_URL env variables should be set in all containers

Runtime

OpenShift

Screenshots

No response

Installation method

chectl/next

Environment

other (please specify in additional context)

Eclipse Che Logs

No response

Additional context

No response

@benoitf benoitf added kind/bug Outline of a bug - must adhere to the bug report template. area/dashboard labels Feb 1, 2022
@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 Feb 1, 2022
@ibuziuk ibuziuk added severity/P2 Has a minor but important impact to the usage or development of the system. sprint/next and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Feb 1, 2022
@ibuziuk ibuziuk mentioned this issue Feb 1, 2022
35 tasks
@amisevsk
Copy link
Contributor

amisevsk commented Feb 2, 2022

Since these URLs are static per-Che installation, another option (rather than injecting them into containers and thus the DevWorkspace) is to use automount functionality in the DevWorkspace Operator. For example, a configmap like

apiVersion: v1
kind: ConfigMap
metadata:
  name: che-devworkspace-env
  labels:
    controller.devfile.io/mount-to-devworkspace: "true"
    controller.devfile.io/watch-configmap: 'true'
  annotations:
    controller.devfile.io/mount-as: env
data:
  CHE_DASHBOARD_URL: "https://my-che-gateway/dashboard/"
  PLUGIN_REGISTRY_URL: "https://my-che-gateway/plugins/v3/"

could be added to the namespace provisioning process and it should result in those env vars being mounted to all containers automatically with no further modifications to DevWorkspaces being required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system. sprint/current
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants