add new certificate health metrics for tekton controllers that use certs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
Feature request
This issue is created as a proactive measure to address situations like #2906. Scope of the issue is to define new metrics to manage certificate health.
Possible metrics:
tekton_proxy_webhook_certificate_reconciliation_failures_total (Certificate Reconciliation Failures)
tekton_proxy_webhook_certificate_expiring_soon (Certificates Expiring Soon (<24h))
tekton_proxy_webhook_certificate_expired
Contributor guide
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 locating the Tekton controllers that use certificates and review issue #2906 for the failure scenario this feature addresses. Confirm the proposed metric names, labels, and semantics, then verify that certificate failures, near-expiry certificates, and expired certificates are represented consistently across the relevant controllers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100