-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Automatic connection to the OpenShift cluster when using the OpenShift connector (no need to login for the user anymore) #20857
Labels
area/plugins
engine/devworkspace
Issues related to Che configured to use the devworkspace controller as workspace engine.
new¬eworthy
For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes
severity/P1
Has a major impact to usage or development of the system.
Milestone
Comments
3 tasks
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
Dec 1, 2021
svor
changed the title
openshift-auth - we won't need this plugin when k8s configuration will be automatically injected into the containers.
Adapt openshift-authentication-plugin to avoid requesting che-server API in devWorkspace
Dec 1, 2021
svor
changed the title
Adapt openshift-authentication-plugin to avoid requesting che-server API in devWorkspace
Adapt openshift-authentication plugin to avoid requesting che-server API in devWorkspace
Dec 1, 2021
svor
added
area/plugins
engine/devworkspace
Issues related to Che configured to use the devworkspace controller as workspace engine.
team/plugins
sprint/current
and removed
status/need-triage
An issue that needs to be prioritized by the curator responsible for the triage. See https://github.
labels
Dec 1, 2021
svor
added
the
severity/P1
Has a major impact to usage or development of the system.
label
Dec 1, 2021
svor
changed the title
Adapt openshift-authentication plugin to avoid requesting che-server API in devWorkspace
[devWorkspace ] Adapt openshift-authentication plugin to avoid requesting che-server API
Dec 1, 2021
moving issue to 7.42 milestone as this issue is part of the endgame |
svor
changed the title
[devWorkspace ] Adapt openshift-authentication plugin to avoid requesting che-server API
[devWorkspace ] Adapt openshift-connector plugin to avoid requesting che-server API
Jan 10, 2022
9 tasks
I've created followup issue for CRW: https://issues.redhat.com/browse/CRW-2640 |
l0rd
changed the title
[devWorkspace ] Adapt openshift-connector plugin to avoid requesting che-server API
Automatic connection to the OpenShift cluster when using the OpenShift connector (no need to login for the user anymore)
Jan 19, 2022
l0rd
added
new¬eworthy
For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes
status/release-notes-review-needed
Issues that needs to be reviewed by the doc team for the Release Notes wording
labels
Jan 19, 2022
sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-2684 |
max-cx
removed
the
status/release-notes-review-needed
Issues that needs to be reviewed by the doc team for the Release Notes wording
label
Jan 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/plugins
engine/devworkspace
Issues related to Che configured to use the devworkspace controller as workspace engine.
new¬eworthy
For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes
severity/P1
Has a major impact to usage or development of the system.
When devWorksapce is enabled, the k8s configuration file should be injected into each container - #20782.
So, in devWorkspace we don't need openshift-authentication-plugin to login into the cluster.
When devWorkspace engine is enabled, we have to provide another che plugin vscode-openshift-connector without che-openshift-authentication-plugin: https://github.com/eclipse-che/che-plugin-registry/blob/main/che-theia-plugins.yaml#L361-L379
Releases Notes Text
Users OpenShift connection token gets automatically injected in the workspace pods as startup and the OpenShift Connector VS Code extension leverages that now. This was already working with the Che server and we have aligned the DevWorkspace based workspaces too.
The text was updated successfully, but these errors were encountered: