ecamp3-logging: make MAX_INDEX_AGE and STORAGE_SIZE configurable #6998
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
In prod the 10Gi were too small for sometimes even more than 1Gi logs per day for 15 days.
manuelmeister
approved these changes
Mar 8, 2025
pmattmann
approved these changes
Mar 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
In prod the 10Gi were too small for sometimes even more than 1Gi logs per day for 15 days.
It is not possible to patch the size of a volumeClaimTemplate directly.
I had to perfom https://serverfault.com/questions/955293/how-to-increase-disk-size-in-a-stateful-set manually.
With this change, we can deploy ecamp3-logging now again on dev and on prod.
I increased the storage for prod now to 50 Gi, and set the index lifetime again to 15 days.