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.

Sign up for GitHub

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

Jump to bottom

Kube context is not added at workspace startup #21454

Closed
Tracked by #21438
l0rd opened this issue Jun 9, 2022 · 1 comment · Fixed by eclipse-che/che-dashboard#562
Closed
Tracked by #21438

Kube context is not added at workspace startup #21454

l0rd opened this issue Jun 9, 2022 · 1 comment · Fixed by eclipse-che/che-dashboard#562
Assignees
@olexii4
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/current

Comments

@l0rd
Copy link
Contributor

l0rd commented Jun 9, 2022 •
edited
Loading

Describe the bug

When I start a workspace and in the terminal I type oc whoami I exepct to get my OpenShift user identifier. Instead I get Che workspace service account:

system:serviceaccount:che-kube-admin-che-o7n1p6:workspace0a8f1b53d0ec4b93-sa

Moreover there is no config file in ~/.kube/ (there is no ~/.kube folder at all):

$ ls ~/.kube/
ls: cannot access '/home/user/.kube/': No such file or directory

Che version

next (development version)

Steps to reproduce

Start a sample workspace, open a terminal and type oc whoami.

Expected behavior

In older version of Che (after 7.42 and in Dev Spaces 3.0 too) the Kube context was setup automatically. c.f. eclipse-che/che-dashboard#431

Runtime

OpenShift
@l0rd l0rd added the kind/bug Outline of a bug - must adhere to the bug report template. label Jun 9, 2022
@l0rd l0rd changed the title Kubernets context is not injected by the dashboard anynmore when I start a workspace Kube context is not added at workspace startup Jun 9, 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 Jun 9, 2022
@l0rd
Copy link
Contributor Author

l0rd commented Jun 9, 2022

@olexii4 @akurinnoy this break some critical scenarios, please have a look.

@l0rd l0rd added 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 9, 2022
@ibuziuk ibuziuk mentioned this issue Jun 10, 2022
Closed
64 tasks
@olexii4 olexii4 self-assigned this Jun 10, 2022
@olexii4 olexii4 mentioned this issue Jun 13, 2022
Merged
@ibuziuk ibuziuk mentioned this issue Jun 27, 2022
Closed
68 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@olexii4 olexii4

Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix kube config flow eclipse-che/che-dashboard
4 participants
@l0rd @ibuziuk @olexii4 @che-bot