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

[Task] Split PVCs #1004

Open
Tracked by #814
andrewazores opened this issue Jan 14, 2025 · 1 comment
Open
Tracked by #814

[Task] Split PVCs #1004

andrewazores opened this issue Jan 14, 2025 · 1 comment
Assignees
Labels
feat New feature or request

Comments

@andrewazores
Copy link
Member

          Could we extract this to a helper method and replace all 3 instances?

On that note, I suppose we can't get away with one PVC since these pods may be scheduled on other nodes and we default to the ReadWriteOnce mode. Maybe we could force all the pods to be on the same node using PodAffinity? We would need to merge this with whatever config the user provides in Scheduling Options, and that could get a bit tricky.

Assuming we stick with 3 PVCs, do you think it would make sense to have separate configurations for each PVC? I could see object storage requiring quite a bit larger size for recordings than the Postgres database. What is the main Cryostat pod's PVC used for now?

Originally posted by @ebaron in #923 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request
Projects
Status: In progress
Development

No branches or pull requests

1 participant