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

Understand and document the steps to safely expand prometheus's disk size, and do so for Pangeo #4811

Closed
3 tasks done
sgibson91 opened this issue Sep 16, 2024 · 2 comments · Fixed by #4886
Closed
3 tasks done
Assignees

Comments

@sgibson91
Copy link
Member

sgibson91 commented Sep 16, 2024

Context

We sometimes need to increase the size of the prometheus disk to accommodate the amount of data we are generating. We should document the steps of how to do this safely so any engineer can perform the task without worrying about running into errors such as below and needing to debug them.

Error: UPGRADE FAILED: cannot patch "support-prometheus-server" with kind PersistentVolumeClaim: persistentvolumeclaims "support-prometheus-server" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize

When we have these steps, we should use them to merge PR #4808

Task list

Tasks

Preview Give feedback

Definition of Done

Pre-defined Definition of Done

  • All the tasks have been completed
  • It has been tested to work and to not break any existing functionality
  • Documentation was added so other engineers can implement this in the future if needed
@haroldcampbell
Copy link

Thi sis dependent on #4810

@sgibson91
Copy link
Member Author

The reason that the steps for expanding the persistentVolume size were not required for pangeo-hubs, is because that cluster is GCP, and all the storage classes there have autoexpansion set to true by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants