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

LEAR: change Postgres db to netapp-block-standard #26052

Open
severinbeauvais opened this issue Feb 19, 2025 · 3 comments
Open

LEAR: change Postgres db to netapp-block-standard #26052

severinbeauvais opened this issue Feb 19, 2025 · 3 comments
Labels
blocked Entities - Olga A label to filter on the tickets for the Entities based team that Olga is PO for.

Comments

@severinbeauvais
Copy link
Collaborator

severinbeauvais commented Feb 19, 2025 •
edited
Loading

The LEAR Postgres database storage class name should be changed from netapp-file-standard to netapp-block-standard.

This should give the db more performance.

lear.png

This requires an outage while the old PVC is taken down and the data is transferred to the new PVC.

best-use-cases.png

This is not needed if the database is migrated to GCP.

(Andriy did this for Pay db.)
@severinbeauvais severinbeauvais added the Entities - Olga A label to filter on the tickets for the Entities based team that Olga is PO for. label Feb 19, 2025
@severinbeauvais
Copy link
Collaborator Author

This should be passed by @pwei1018 .

@pwei1018
Copy link
Collaborator

Both the Entity and Names teams are working on the migration. This action may be risky. I’d prefer not to make changes in OCP at this time.

@severinbeauvais
Copy link
Collaborator Author

Patrick added:

image.png

@severinbeauvais severinbeauvais mentioned this issue Feb 21, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked Entities - Olga A label to filter on the tickets for the Entities based team that Olga is PO for.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@severinbeauvais @pwei1018