HubRegistrationReadinessHealthCheck
Namespace: Meshmakers.Octo.Sdk.Common.Adapters
The readiness decision shared by dedicated adapters and adapter pool members: ready while registered on a live connection, and during a startup grace period before the first registration.
public abstract class HubRegistrationReadinessHealthCheck : IHealthCheck
Inheritance Object → HubRegistrationReadinessHealthCheck
Implements IHealthCheck
Remarks:
Two deliberate softeners keep this from becoming a hair trigger:
AdapterOptions.HubReadinessGracePeriod — a fresh pod is ready while it is still working on its first registration (connect, token, controller rollout), so it is never taken out of service before it ever had a chance.
AdapterOptions.HubReadinessProbeEnabled — an escape hatch for deployments that must stay ready without a controller connection.
A brief reconnect is additionally absorbed by the probe's own failureThreshold in the
chart.
Methods
CheckHealthAsync(HealthCheckContext, CancellationToken)
public Task<HealthCheckResult> CheckHealthAsync(HealthCheckContext context, CancellationToken cancellationToken)
Parameters
context HealthCheckContext
cancellationToken CancellationToken