Access the management cluster

The management cluster is where you create, update, and scale your clusters. Your apps don't run here: they run on the workload clusters you create from it. See Create a cluster .

This page walks you through setting up a kubeconfig for the management cluster: you copy the template below, which fills in your namespace when you're logged in. Otherwise, use the namespace from your account setup email. If you don't have an account yet, see How do I get access and start? first.

Configure your kubeconfig

Create a file to store the `kubeconfig` in

Copy this configuration into the file

Loading protected content…

Set your namespace

Use the namespace from your account setup email in the kubeconfig.

Restrict the file permissions

Run chmod 600 FILENAME.

Export `KUBECONFIG`

Run export KUBECONFIG=<path/to/file>.

If you want to make this your default kubeconfig, you can move it to the ~/.kube/config file.

Access Syself Autopilot

To access the management cluster, you need kubelogin installed. Run kubectl get clusters. This opens your browser to authenticate. Once you are logged in, kubectl works as usual.

Note

If this is your first time using Syself Autopilot, the output of kubectl get clusters will be No resources found in org-your-company namespace.. This is not an error, it just means no clusters have been created yet under your organization.

Optional: Log out

You might have to authenticate yourself again, if the token (and refresh token) expires. In case you want to invalidate the current session and remove access to the management cluster, you can use rm -rf ~/.kube/cache/oidc-login.

Next step

With access to the management cluster in place, prepare the Hetzner account your clusters will run in: Connect your Hetzner account .

Prerequisites

Install kubectl and kubelogin on Linux, macOS, or Windows before connecting to your Syself Autopilot management cluster. Includes version verification steps.

Connect your Hetzner account

Prepare your Hetzner account for Syself Autopilot - create a project and API token, upload an SSH key, and store the credentials as secrets in the management cluster.