Switch Parca storage backend to GCS #887
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change migrates Parca's storage backend from local filesystem (emptyDir) to Google Cloud Storage for persistent profile storage. The implementation includes: - Updated Parca ConfigMap to use GCS bucket configuration - Added volume mount for GCS service account credentials - Removed temporary emptyDir storage volume - Added documentation for required external secret setup The deployment now requires a Kubernetes secret named 'parca-gcs-service-account' containing the GCS service account key JSON to be created separately. Signed-off-by: Matthias Loibl <mail@matthiasloibl.com>
metalmatze
force-pushed
the
parca-gcs-storage
branch
from
9d7c647 to
a2a41e2
Compare
Member
Author
|
I'm not sure I can create the necessary secret. I would need some more time to check this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes
Configuration Requirements
This deployment requires a Kubernetes secret named
parca-gcs-service-accountcontaining a GCS service account key JSON file. The secret should be created separately with appropriate permissions to read/write to the configured GCS bucket (prometheus-parca-profiles).