Accessing the management cluster
Configure your kubeconfig#
Create a file to store the
kubeconfiginCopy this configuration into the file
Loading protected content…Change the namespace of the kubeconfig and add your organization name to it.
Use
chmod 600 <filename>to set the permissions for the file.Export the kubeconfig to use it via
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 to have kubelogin installed. Use kubectl get clusters. This will open your browser for authentication. After successful authentication, you will be able to use kubectl as always!
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.