Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

local/staging: add prometheus-es-exporter for 7.10 cluster #1068

Merged
merged 1 commit into from
Aug 9, 2023
Merged

local/staging: add prometheus-es-exporter for 7.10 cluster #1068

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions k8s/helmfile/env/local/prometheus-elasticsearch-exporter-1.values.yaml.gotmpl
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
resources:
requests:
cpu: 125m
memory: 156Mi
limits:
cpu: 125m
memory: 256Mi
23 changes: 23 additions & 0 deletions k8s/helmfile/env/production/prometheus-elasticsearch-exporter-1.values.yaml.gotmpl
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
es:
uri: http://elasticsearch-1.default.svc.cluster.local:9200
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we gave up on the idea of using a headless service because we just don't know which one to monitor, correct?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we can find out where this service is pointing at?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was too unclear in the commit message. This service is identical to the h1 coordinator service. I assume both are "headful"? but maybe this is fine. There doesn't appear to be a need for a headless discovery service with this node configuration unlike the "elasticsearch upstream" chart

timeout: 90s

resources:
requests:
cpu: 250m
memory: 1.25Gi
limits:
cpu: 250m
memory: 2Gi

serviceMonitor:
scrapeTimeout: 50s
interval: 60s
enabled: true
labels:
release: kube-prometheus-stack
metricRelabelings:
- sourceLabels: [cluster]
targetLabel: es_cluster
- regex: ^cluster$
action: labeldrop
7 changes: 7 additions & 0 deletions k8s/helmfile/env/staging/prometheus-elasticsearch-exporter-1.values.yaml.gotmpl
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
resources:
requests:
cpu: 250m
memory: 512Mi
limits:
cpu: 250m
memory: 512Mi
7 changes: 7 additions & 0 deletions k8s/helmfile/helmfile.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,6 +226,13 @@ releases:
version: 5.2.0
<<: *default_release

- name: prometheus-elasticsearch-exporter-1
namespace: monitoring
chart: prometheus-community/prometheus-elasticsearch-exporter
installed: {{ ne .Environment.Name "production" | toYaml }}
version: 5.2.0
<<: *default_release

- name: istio-service-mesh
namespace: istio-system
chart: ./../../charts/istio-service-mesh
Expand Down