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

OpenShift token retrieval from Keycloak should happen only once during workspace startup/suspension #19724

Closed
skabashnyuk opened this issue Apr 30, 2021 · 1 comment
Labels
area/che-server 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.

Comments

@skabashnyuk
Copy link
Contributor

Is your task related to a problem? Please describe.

During workspace startup we performing multiple k8s operations.
For each operation, we requesting a keycloak for the new OpenShift token.
Some delays might happen between operations: image pulling, etc.
As a result, we might face the issue when the keycloak token is no longer valid.

Describe the solution you'd like

OpenShift token retrieval from Keycloak should happen only once during workspace startup/suspension

Describe alternatives you've considered

n/a

Additional context

https://issues.redhat.com/browse/CRW-1767

@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. area/che-server sprint/next labels Apr 30, 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 Apr 30, 2021
@JPinkney JPinkney 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 May 3, 2021
@skabashnyuk
Copy link
Contributor Author

won't fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-server 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.
Projects
None yet
Development

No branches or pull requests

3 participants