Mukul SharmaandClaude Opus 5
df3e0a41af
Disk, not memory. The volume sits at 1.4G of 2.9G at seven days, and every extra day is charged against the project's shared 250GB SSD quota. Three days still spans a weekend, which is the window that matters for working out what happened to something overnight. Worth being explicit about what this does not do, since it followed an OOM-kill and could easily be mistaken for the fix: retention has no bearing on the memory this needs. That tracks active time series and cache size, neither of which depends on how long data is kept — which is why the limit had to be raised rather than this lowered when it started OOM-killing on restart. Lowering this now would not let that be undone. The lever for memory, if it is ever needed, is scrape cardinality. Several targets here emit more than forty labels per series, which VictoriaMetrics warns about in its own log; dropping labels there reduces series count directly, and with it the memory. Old partitions are removed on VictoriaMetrics' own cycle rather than at startup, so the disk figure falls over the following hours, not immediately. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LEsTefWWifp4ikvhHF5s6N
devops-infra-helm-charts
This branch (main) is part of the restructuring process for the gcp-devops-admin repository, aimed at organizing helmcharts of all infrastructure tools and their corresponding value files. The purpose of this repository is to centralize and manage these resources efficiently.
Directory Structure
helm-templates
This directory is intended for caching or forking helm charts locally. If there's a need to modify or customize any helm chart, it can be done here. Otherwise, the charts will be used directly from the provider.
helm-overrides
The helm-overrides folder stores custom values files for helm charts. These files can be used to override the default values provided by the helm charts, whether they are forked or used directly from the provider.
cluster_name
Each tool within the repository may have different values based on the specific clusters. This directory is used to manage configurations and values tailored to different clusters.
manifests
The manifests directory contains manifest files that need to be applied only once. Examples include service-to-service configurations, storage classes, and any other manifest-related files necessary for the operation of the infrastructure tools.
Additional Notes
Please ensure that all changes made to this branch align with the restructuring objectives and follow the best practices for managing helm charts and infrastructure-related configurations.
For any questions or concerns, please reach out to the designated repository maintainers.