Provide trusted metrics TLS configuration
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 9h 55m
- Merged PRs (30d)
- 25
Description
Add a complete production metrics TLS overlay. It must create or reference a trusted certificate, configure the manager mount and metricsCertPath, set ServiceMonitor serverName and CA references, and remove the need for insecureSkipVerify. Add build or integration validation for the overlay.\n\nCurrent templates: config/prometheus/monitor_tls_patch.yaml and config/default/cert_metrics_manager_patch.yaml
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
Start by reading config/prometheus/monitor_tls_patch.yaml and config/default/cert_metrics_manager_patch.yaml to understand the existing overlay and certificate wiring. Trace how the manager mount, metricsCertPath, ServiceMonitor serverName, and CA references are configured, then add build or integration validation. Done means the overlay uses a trusted certificate and no longer needs insecureSkipVerify.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure, observability-sre, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100