cockroachdb / cockroachdb/helm-charts

Prometheus can't scrape the endpoint because of the ever changing pod IP

Open
#37 2 comments 4 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
105
Forks
152
Avg merge
4d 23h
Merged PRs (30d)
5

Description

When using secure installations, and your own certificates, Prometheus will fail the scrapping because the pod IP was not in the original CSR.

The error on Prometheus looks like this:

```
Get https://10.6.26.160:8080/_status/vars: x509: certificate is valid for 127.0.0.1, not 10.6.26.160
```

I propose #36 to fix the problem.

Jira issue: HELM-38

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the proposed fix in issue #36 and reviewing how the secure installation handles certificates for the Prometheus endpoint. Use the shown x509 error and changing pod IP scenario to verify the behavior. Done means Prometheus can scrape the endpoint without certificate validation failing for the pod IP.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes, prometheus
Domain
devops, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.