Repository navigation
Conversation
Add an opt-in loopback HTTP metrics endpoint backed by an isolated Prometheus registry for local OpenTelemetry collection. Start it independently of etcd and API-server readiness, bound scrape requests, and keep listener failures non-fatal. Share certificate chain construction and pending metadata parsing with a read-only observation path. Coordinate through a non-creating shared lock without reading private keys, generating certificates, or recovering transactions. Publish minute-based snapshots of active certificate validity and five-state health, pending renewal, collection success, and last-success time. Omit unavailable series instead of presenting stale health or unknown pending state as a reliable zero. Add startup-loaded metrics configuration with loopback validation, regenerate configuration and schema, document access and failure semantics, and include focused Go tests and Robot smoke coverage. Co-authored-by: GPT-5 <noreply@openai.com> Signed-off-by: ehila <ehila@redhat.com>
Accept a variadic list of collectors through an interface that embeds prometheus.Collector and adds context-aware background collection. Register and start each collector independently, and cancel their shared context when the service stops. Remove the separate registration method, exercise multiple collector lifecycles in the existing service test, and update the contributor architecture documentation. Co-authored-by: GPT-5 <noreply@openai.com> Signed-off-by: ehila <ehila@redhat.com>
Signed-off-by: ehila <ehila@redhat.com>
Package a loopback MicroShift scrape drop-in with the observability RPM, preserving administrator edits with config(noreplace). Reuse the existing scrape pipelines and host resource detection across the small, medium, and large presets while keeping endpoint enablement opt-in. Extend the observability Robot suite to verify certificate, pending-renewal, and freshness metrics reach the collector and backend. Document enablement, custom targets, upgrade adoption, host identity, and disabled-target behavior. Co-authored-by: GPT-5 <noreply@openai.com> Signed-off-by: ehila <ehila@redhat.com>
|
@eggfoobar: This pull request references OCPEDGE-3133 which is a valid jira issue. DetailsIn response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Pipeline controller notification This PR uses the pipeline controller for second-stage tests. Selection and triggering follow the repository configuration. Use |
|
/hold Holding until #7641 has merged in |
|
No actionable comments were generated in the recent review. WalkthroughMicroShift adds a disabled-by-default, loopback metrics endpoint for certificate status and renewal data. The change adds read-only certificate observation, Prometheus collection and serving, configuration, observability packaging, and tests. ChangesLocal Certificate Metrics
Estimated code review effort: 4 (Complex) | ~45 minutes Change: Feature Sequence Diagram(s)sequenceDiagram
participant MicroShift as RunMicroshift
participant MetricsService
participant CertificateCollector
participant Observe
participant CertificateStore
participant ScrapeClient
MicroShift->>MetricsService: Register service and certificate collector
MetricsService->>CertificateCollector: Run collector
CertificateCollector->>Observe: Refresh with current time
Observe->>CertificateStore: Read lock, inventory, and pending metadata
ScrapeClient->>MetricsService: GET /metrics
MetricsService->>CertificateCollector: Collect cached snapshot
CertificateCollector-->>MetricsService: Return metrics
MetricsService-->>ScrapeClient: Return metrics
Merge Risk:
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@eggfoobar: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Summary by CodeRabbit