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

[devworkspaces] Not able to start a devworkspace because namespace are not found #20014

Closed
skabashnyuk opened this issue Jun 22, 2021 · 2 comments · Fixed by eclipse-che/che-dashboard#293
Assignees
Labels
area/dashboard kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/current
Milestone

Comments

@skabashnyuk
Copy link
Contributor

Is your task related to a problem? Please describe.

Not able to start a devworkspace because namespace are not found

Describe the solution you'd like

Steps to reproduce

  1. Deploy che on k8s with devworkspaces
  2. Enable unsupported k8s API on che server.
    kubectl patch checluster/eclipse-che --patch "{"spec":{"server":{"customCheProperties": {"CHE_INFRA_KUBERNETES_ENABLE__UNSUPPORTED__K8S": "true"}}}}" --type=merge -n eclipse-che
  3. Try to start devworkspaces

Знімок екрана 2021-06-22 о 16 37 33

Describe alternatives you've considered

Additional context

@skabashnyuk skabashnyuk added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Jun 22, 2021
@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 Jun 22, 2021
@JPinkney
Copy link
Contributor

The devworkspace-client currently only initializes namespaces on OpenShift: https://github.com/che-incubator/devworkspace-client/blob/main/src/browser/che-api.ts#L35, we still need to add support for kubernetes

@metlos metlos added area/dashboard status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jun 22, 2021
@sleshchenko sleshchenko added this to the 7.33 milestone Jun 22, 2021
@sleshchenko
Copy link
Member

it should be easy fix, adding to the current sprint as unplanned to unblock moving forward in the direction of DevWorkspace support on Kubernetes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
5 participants