eks.clusters.availability

The month’s measured API availability, SLA result and credit, each unavailable minute and which measurement saw it, and the outside probes

GET /eks/api/clusters/{cluster}/availabilityIAM eks:DescribeClusterRead

A minute is unavailable when no control-plane machine reported a serving API (agent), or a strict majority (at least two) of Deutsche Cloud’s outside probe locations failed `GET /readyz` (outside). A minute with no machine report at all while at least two outside locations all got answers is Deutsche Cloud’s blind spot: listed with source `ews-blind-spot`, counted as available (`blindSpotMinutes`). `probes` is the last decided minute per location; `platformAddresses` are the addresses those requests come from, let through the endpoint while it is public.

Request syntax

GET /eks/api/clusters/{cluster}/availability

Path parameters

  • clusterRequired

    string

    Constraints: /^(ewk-[0-9a-f]{12}|[a-z]([a-z0-9-]{0,38}[a-z0-9])?)$/

Query parameters

  • monthOptional

    string

    YYYY-MM (UTC); default: this month

    Constraints: /^\d{4}-(0[1-9]|1[0-2])$/

Response

200 with { month, sampledMinutes, unavailableMinutes, percent (null with nothing sampled), slaPercent (99.9 for standard, null for dev), creditPercent, agentUnavailableMinutes, outsideUnavailableMinutes, blindSpotMinutes, closed (the month’s SLA result once closed: at, feeBase, creditPercent, creditAmount, credited, note; else null), outsideProbe { enabled, reason }, minutes (each unavailable minute, newest first, at most 500: minute, source, detail), probes (minute, location, ok, statusCode, latencyMs, error), platformAddresses (empty while the public endpoint is off) }. 404 when no cluster has that id or name, 403 without the permission on it (eks:DescribeCluster).

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow eks:DescribeCluster on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud eks clusters availability cluster

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_eks_clusters_availability.