Programmatic Endpoints for Managed Kubernetes

This article lists the region-specific endpoints for interacting with Managed Kubernetes through the API, CLI, Swagger, and Terraform. All programmatic operations, including creating clusters and node pools, run in a specific cloud region. Choose the matching endpoint and use it consistently across all tools.

Regional endpoints

Choose your region first, then use the matching endpoint format for your tool.

R1

API / CLI (full URL): https://mks.r1.cloud.eumetsat.int/api/v1
API Docs (browser): https://mks.r1.cloud.eumetsat.int/swagger
Terraform provider endpoint (host:port): mks.r1.cloud.eumetsat.int:443

R2

API / CLI (full URL): https://mks.r2.cloud.eumetsat.int/api/v1
API Docs (browser): https://mks.r2.cloud.eumetsat.int/swagger
Terraform provider endpoint (host:port): mks.r2.cloud.eumetsat.int:443

FRA1-3

API / CLI (full URL): https://mks.ela.cloud.eumetsat.int/api/v1
API Docs (browser): https://mks.ela.cloud.eumetsat.int/swagger
Terraform provider endpoint (host:port): mks.ela.cloud.eumetsat.int:443

Endpoint formats

Use the format required by your tool:

API / CLI: the full URL ending with /api/v1, followed by the exact API path, for example /clusters.
Swagger: the URL ending with /swagger. Open it in your browser.
Terraform: the host:port endpoint ending with :443.

Authentication tokens

You need access to the selected region and a valid token for every tool that makes API calls:

API / CLI endpoint: a token is required for requests. Without it, the API typically returns 401 Unauthorized.
Terraform provider endpoint: a token is required because Terraform calls the same API.
Swagger: a token is usually not required to open the documentation page, but it is required to execute protected requests with Try it out.

To obtain a Managed Kubernetes API token, see Obtain Managed Kubernetes API token.