Problem
When a leased exporter goes offline (maintenance, power outage, network issue), the lease remains Ready but the exporter is unreachable. Users who only check their lease — which is most users — have no way to know the exporter is offline without separately inspecting the exporter object.
The combination of lease:Ready + exporter:Offline tells the full picture, but users shouldn't need to check two resources to understand the health of their session.
Proposal
Add an ExporterOnline condition to the Lease status. The lease controller watches the bound exporter's Online condition and mirrors it:
Type: ExporterOnline Status: False Reason: ExporterOffline
Message: "Bound exporter 'lab-board-1' is offline since ..."
- The lease phase stays
Ready (reservation is preserved)
- The new condition signals degradation without changing lease semantics
- Follows the standard Kubernetes pattern of multiple coexisting conditions
- Visible to all consumers: CLI, kubectl, dashboards
Context
Problem
When a leased exporter goes offline (maintenance, power outage, network issue), the lease remains
Readybut the exporter is unreachable. Users who only check their lease — which is most users — have no way to know the exporter is offline without separately inspecting the exporter object.The combination of
lease:Ready+exporter:Offlinetells the full picture, but users shouldn't need to check two resources to understand the health of their session.Proposal
Add an
ExporterOnlinecondition to the Lease status. The lease controller watches the bound exporter'sOnlinecondition and mirrors it:Ready(reservation is preserved)Context