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

CRW Openshift Connector plugin - inClusterUser does not have access to cluster projects #17626

Closed
6 of 22 tasks
ScrewTSW opened this issue Aug 12, 2020 · 4 comments
Closed
6 of 22 tasks
Labels
kind/bug Outline of a bug - must adhere to the bug report template. status/duplicate Issue identified as a duplicate of another issue

Comments

@ScrewTSW
Copy link
Member

Describe the bug

By default, the openshift-connector-plugin does not work with CRW.
The pre-logged-in user does not see the projects that are available on the cluster.
There is no way to create new projects without the plugin being re-logged in with a different user from the cluster.

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

  • Start any workspace
  • Press CTRL+Shift+J
  • Install openshift-connector-plugin and reload the workspace
  • Open openshift-connector plugin section on the left side of the IDE
  • Wait for the plugin to load
  • Empty cluster is displayed
  • Right-click on the cluster and logout
  • Login with cluster admin account
  • The projects are now visible and you can create your own projects in the namespaces

Expected behavior

  • Required and proper project is displayed to the inClusterUser account and appropriate permissions are set

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift
Client Version: 4.3.5
Server Version: 4.5.5
Kubernetes Version: v1.18.3+08c38ef
  • minikube (include output of minikube version and kubectl version)
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • other: (please specify)

Screenshots

To be added

Installation method

  • chectl
    • provide a full command that was used to deploy Eclipse Che (including the output)
    • provide an output of chectl version command
  • OperatorHub
  • I don't know

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other - ocp45.crw-qe.com
  • other: please specify

Eclipse Che Logs

N/A

Additional context

N/A

@ScrewTSW ScrewTSW added kind/bug Outline of a bug - must adhere to the bug report template. status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Aug 12, 2020
@sunix
Copy link
Contributor

sunix commented Aug 12, 2020

Hello,
In Che #15261 it should work
If you have the issue with CRW, please open a issue in https://issues.redhat.com/browse/CRW

@l0rd
Copy link
Contributor

l0rd commented Aug 12, 2020

Closing as this has been fixed on Che 7.12 and from what I understand you are testing latest CRW (2.2) that is based on Che 7.9.x.
If that's a CRW 2.3 issue please open an issue on CRW Jira.
If that's a Che 7.12 or higher issue please re-open this issue.

@l0rd l0rd closed this as completed Aug 12, 2020
@l0rd l0rd added status/duplicate Issue identified as a duplicate of another issue and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Aug 13, 2020
@MichalMaler
Copy link
Contributor

CRW issue is here
https://issues.redhat.com/browse/CRW-1158. It should be actual for 2.3

@ScrewTSW
Copy link
Member Author

@l0rd yes, the issue is opened in Jira that @MichalMaler linked. It's related to latest CRW 2.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. status/duplicate Issue identified as a duplicate of another issue
Projects
None yet
Development

No branches or pull requests

4 participants