Mukul SharmaandClaude Opus 5
6677c9e315
The other three disabled subcharts (alertmanager/kube-state-metrics/ pushgateway) stay off — none of them do anything cAdvisor's per-container metrics don't already cover for this deployment's actual purpose. node-exporter is different: it's the one thing here that would report on the node itself (disk, memory, load) rather than any particular container, which matters on an 8GB single node already near its ceiling. One DaemonSet pod, hostNetwork rather than a Service, resources capped at 32Mi/64Mi — light enough that turning it on doesn't meaningfully touch the budget the other three would have. Verified with `helm template`: the DaemonSet renders with hostNetwork/ hostPID true and the trimmed resources, and its Service carries the `prometheus.io/scrape: true` annotation the server's already-enabled kubernetes-service-endpoints job picks up automatically — no separate scrape config needed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wajog7nELA3i8JWTjxYGHF
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.