generate and manage certificates for prometheus node_exporter TLS and client certificate authentication
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 4
- Forks
- 15
- Avg merge
- 1h 50m
- Merged PRs (30d)
- 4
Description
the monitoring host should have a certificate that is compatible with prometheus node_exporter client certificate authentication so that it can use certificate based authentication on nodes outside of AWS. A self-signed CA should be created for prometheus metrics collection; certificates issued for the monitoring host and node_exporter endpoints, e.g. a web_config.yml configured that points at the ca.cert, endpoint.cert, and authenticates by a certificate issued by that ca for the monitoring host.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name repository files or tests. Start by locating the Prometheus and node_exporter configuration, then determine how certificates are currently provisioned; done means a self-signed CA issues certificates for the monitoring host and node_exporter endpoints, with web_config.yml referencing ca.cert and endpoint.cert and enabling client certificate authentication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus
- Domain
- observability, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100