Mukul SharmaandClaude Opus 5
f6c659dd4b
It had run for weeks at 128Mi/512Mi and then OOM-killed in a loop the first time anything restarted it — exit 137 about fifty seconds after a clean start, repeatedly. Nothing about its configuration had changed. The dataset had grown to 3.14 billion rows, and the memory needed to resume ingestion no longer fit in the limit. That failure mode is worth naming: a long-lived pod can sit comfortably past the limit it would need in order to start again, so the problem stays invisible until something restarts it — here, an unrelated sync adding a hostname. The limit was not wrong when it was written; it was outgrown. Memory tracks active time series rather than disk, so shortening retentionPeriod would not have helped — the same targets are scraped either way, and several carry more than forty labels. Affordable: memory requests across the three nodes sit at 62%, 18% and 47%. CPU is what is scarce here, and this costs none. 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.