-
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
Decommissioning PostgreSQL database #21374
Comments
Duplicate #21183? |
yeah, we can either close the original or add the details to it ;-) |
PR for the first phase of decommissioning eclipse-che/che-server#398 |
Can we add switching to rolling update deployment strategy for che-server as a subtask of this issue? |
we probably can track it separately as part of #7662 - verify and switch to rolling update once db is decommissioned. The current issue looks like a pre-req, not a sub-task for the roling update epic |
Waiting for the final docs PR to be merged before resolving the issue eclipse-che/che-docs#2561 |
Docs PR has been merged. Closing |
sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-4105 |
Is your task related to a problem? Please describe
PostgreSQL database does not store relevant data anymore. Whereas some of the date might still be used the vast majority of it is either irrelevant or outdated e.g. #21168 (comment)
After the keycloak deprecation, the next logical step is the deprecation of the PostgreSQL database.
Describe the solution you'd like
Decommissioning PostgreSQL database completely from Eclipse Che codebase. We need to figure out which relations are still in use and have a clear plan for database removal:
Describe alternatives you've considered
N/A
Additional context
Additional motivation for removing db is the fact that users are deprovioned every 30 days according to the TOS on Developer Sandbox, and during the de-provioning toolchain needs to explicitly cleanup the users entries from the Eclipse Che db. In the latest version of Eclipse Che we need to let OpenShift handle the user management instead.
In general, once decommissioned it will be much less codebase to support and -1 operand to manage.
The text was updated successfully, but these errors were encountered: