This guide addresses an issue accessing the API Server that may occur when using Kubernetes as a Service (KaaS) on Infomaniak Public Cloud.

Preamble

• As part of Kubernetes as a Service, the SSL certificate allowing connection to the API Server (the management interface for the client) is renewed once a year.
• Check for any ongoing issues on https://status.infomaniak.cloud/.

API Server inaccessible

If the certificate has been renewed, you may no longer be able to connect to your cluster. If you are using the CLI tool kubectl, the following error may appear:

"Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"

Resolution of the issue

To resolve this issue, you must update your access credentials according to your deployment method.

1. Via the Infomaniak Manager (manual use)

It is necessary to re-download the updated Kubeconfig file:

1. Click here to access the management of your cluster on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product concerned:
3. Download the new Kubeconfig file.
4. Replace your old local file (usually ~/.kube/config).

2. Via Terraform (Infrastructure as Code)

If you manage your infrastructure with Terraform, the expected behavior is as follows:

• The provider should normally automatically retrieve the new Kubeconfig during the read step (read).
• When retrieving the state or running a terraform plan, the tool will refresh the data and download the new version of the certificate from the Infomaniak API.

Also refer to the official Public Cloud documentation for more information on managing your resources.