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

Introduction

• As part of Kubernetes as a Service, the SSL certificate that enables connection to the API Server (the management interface for the client) is renewed once a year.
• Check for any ongoing issues at 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 kubectl CLI tool, 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"

Troubleshooting

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

1. Via the Infomaniak Manager (manual configuration)

You need 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 in question.
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:

• Enter the terraform refresh command.
• The provider should normally automatically retrieve the new Kubeconfig during the read step.
• 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.