This guide will help you troubleshoot any issues you may encounter when activating your Windows Server license.

Introduction

• Check for any ongoing issues at https://infomaniakstatus.com/.
• Specifically for Public Cloud, the list of scheduled maintenance and ongoing issues can be found at https://status.infomaniak.cloud/.

Modify the registered key

Open the Run utility (Windows logo key + R).

Remove the registered key

Run the following command:

cscript.exe c:\windows\system32\slmgr.vbs -upk

Add a new key

Restart the Run utility, then execute the following command:

cscript.exe c:\windows\system32\slmgr.vbs -ipk {KEY}

by replacing {KEY} with the key from your configuration below:

Activate Windows

Restart the Run utility, then run the following command to associate the key with the Infomaniak activation server:

cscript.exe c:\windows\system32\slmgr.vbs -skms kms.infomaniak.cloud

Restart the Run utility, then finally execute the following command to activate your Windows system:

cscript.exe c:\windows\system32\slmgr.vbs -ato

This guide explains the process for withdrawing and restoring assets when a Public Cloud product is terminated.

Withdrawing and Restoring Assets on Public Cloud

When a voluntary termination is performed, the resources associated with the Public Cloud are gradually deactivated and then deleted.

DNS resources of the DNSaaS (Designate) type are immediately deleted upon termination.

Other resources are deactivated across all Public Cloud regions:

• users and projects are deactivated;
• access to the remaining resources is no longer possible;
• resources that are still exposed are deactivated:
  • S3 buckets and Swift containers (Object Storage);
  • stopped Compute instances (power-off);
  • automatic exit from pause mode before instance shutdown;
  • automatic exit from rescue mode before instance shutdown;
  • deactivation of Load Balancers (LBaaS);
  • deactivation of orchestrations and alarms (Heat).

Resources that are not exposed are not immediately modified, including:

• volumes;
• images;
• backups;
• snapshots;
• public keys;
• private networks;
• secrets.

Asset Retention Period

With the exception of DNS resources, assets are retained for a period of 7 days after termination.

On the 7th day at 3:00 AM, all remaining resources are permanently deleted, with no possibility of restoration.

Restoring Assets After Termination

After the product is terminated, a request for restoration can be made within a maximum period of 3 calendar days.

This request requires:

• an active subscription to a Public Cloud product;
• an up-to-date billing status;
• compliance with the applicable contractual terms.

Provided that the data is still available on the storage infrastructure, suspended services can be reactivated within a maximum period of 4 days after the request is approved.

Stopped instances are not restarted automatically. However, they can be restarted manually if necessary.

Exporting assets remains your responsibility.

This guide explains how to transfer an instance to another physical machine within Infomaniak's Public Cloud.

Introduction

• This operation can be performed at any time and offers several advantages:
  • anticipate or avoid planned maintenance;
  • distribute the load across multiple hosts;
  • improve the stability or performance of an instance.

Migrate the instance to another physical machine…

… since Horizon

1. Click here to access the management of your product in the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question:
   
3. Click on the Horizon shortcut to connect to it:
   
4. In the Instances menu, click on the action menu ⋮ located to the right of the instance to be transferred.
5. Click on Transfer an instance (Migrate):
   
6. Confirm the transfer:
   
7. Check the current status and wait a few minutes:
   
8. Confirm the migration:
   
9. Wait for the operation to complete before restarting or modifying the instance.

… via the command line (CLI)

1. List your available instances:
   openstack server list
2. Identify the ID of the instance to be transferred (ID column).
3. Start the migration to another physical host:
   openstack server migrate <instance_ID>
   This command triggers the movement of the instance to a new host within the cluster.
4. Check the migration status:
   openstack server show <instance_ID>
   The instance will then enter the RESIZED state when the migration is complete but not yet confirmed.
5. Once the migration is complete and validated, confirm the transfer:
   openstack server resize --confirm <instance_ID>
   or, depending on the OpenStack client version:
   openstack server migration confirm <instance_ID>
   
   • If the server migration confirm command displays a warning indicating that it is deprecated, the process will still run in the background and the confirmation will be taken into account.
   • If you get an error like:
     Cannot 'confirmResize' instance ... while it is in vm_state active (HTTP 409)
     this means that the migration has already been confirmed (manually or automatically).
6. You can also cancel the migration if a problem is detected before confirmation:
   openstack server resize --revert <instance_ID>
   or:
   openstack server migration revert <instance_ID>
7. If no manual action is performed, the migration is automatically confirmed after 24 hours. The instance status then reverts to ACTIVE.

Infomaniak does not directly provide a VPN, tunnel, or secure network built between two points (VPN = Virtual Private Network). However, you can consider an alternative solution using Infomaniak services such as Public Cloud. This guide explains how to use this Infomaniak hosting product to create a VPN.

Create a VPN with Infomaniak Public Cloud

Infomaniak offers the use of one of the following alternatives to allow you to create a VPN VM manually:

• setting up a VPN via IPsec
• setting up a VPN via the OPNSense tool

This guide lists the different Linux distributions and Windows versions that you can deploy with one click when launching a new instance of your Public Cloud.

Available operating systems

The images of the different operating systems offered by Infomaniak in the Images section and used in the Source section when launching a new instance of your Public Cloud are currently as follows:

• Alpine Linux 3.17
• Amazon Linux 2
• Arch Linux
• CentOS 7
• CentOS 8 Stream
• CentOS 9 Stream
• CirrOS 0.6.1
• Debian 10.13 buster
• Debian 11.6 bullseye
• Fedora Cloud OS 37
• Fedora Core OS 37
• FreeBSD 13.1
• Infomaniak Rescue Image
• OPNsense 22.1.2_2-amd64
• Oracle Linux 9
• RancherOS 1.5.8
• RedHat Enterprise Linux 9
• Rocky Linux 9
• Ubuntu 18.04 LTS Bionic Beaver
• Ubuntu 20.04 LTS Focal Fossa
• Ubuntu 22.04 LTS Jammy Jellyfish
• openSUSE Leap 15.4 JeOS
• Microsoft Windows Server 2019 Standard
• Microsoft Windows Server 2019 Datacenter
• Microsoft Windows Server 2022 Standard
• Microsoft Windows Server 2022 Datacenter
• Microsoft Windows Server 2025 Standard
• Microsoft Windows Server 2025 Datacenter

When deploying, be sure to always prioritize the image ID over its name.

This guide addresses an issue that may occur when starting an instance on Public Cloud Infomaniak.

Preamble

• Check for any ongoing issues on https://infomaniakstatus.com/.
• For Public Cloud specifically, the list of scheduled maintenances and ongoing issues is available at https://status.infomaniak.cloud/.

Using Image IDs

The images of the different operating systems, offered by Infomaniak in the Images section and listed in the Source section when you launch a new instance of your Public Cloud, are regularly updated but without changing their name:

Having a stable name can cause issues with automation tools like heat or terraform with the risk that they recreate the VMs unintentionally.

This issue can be avoided by using the image ID or a personal image:

This guide explains the differences between Infomaniak's web hosting plans to help you choose the best solution based on your IT needs.

1. Site Creator

Standalone plans, independent of a hosting solution such as the one presented in point 3.

Site Creator is a ready-to-use solution that allows you to easily create a showcase website, a blog, or an e-commerce store without any specific technical skills. Offered as a standalone solution (without requiring traditional web hosting), it is available in several plans to suit your needs:

• Site Creator Free: a free version to test and customize a web page with basic features
• Site Creator Lite: ideal for publishing a showcase website or blog (up to 6 web pages, 15 GB of disk space, and a free domain name for 1 year)
• Site Creator Pro: the complete solution for online stores (unlimited pages, 50 GB of disk space, e-commerce features with payment and inventory management, free domain name for 1 year)

Learn more about the Site Creator plans and compare features.

2. Web Hosting Starter

Simple and free web hosting

The Starter web hosting plan is offered free of charge with every domain name registered with Infomaniak. It offers 10 MB of disk space to create a website (basic pages in HTML only - no PHP, no database) even without specific knowledge, thanks to the Welcome Page tool.

• Register or transfer a domain name to Infomaniak
• Learn more about the benefits included with a domain name

3. Shared Web Hosting

The flagship offer for creating your websites

These web hosting solutions are shared hosting offers (websites will be hosted on servers whose resources are shared with other customers). To guarantee the reliability of these shared services, Infomaniak servers use, on average, only 40% of the CPU power and are equipped with professional, latest-generation SSD disks.

Web hosting offers a minimum of 250 GB of disk space and allows you to manage multiple websites with multiple domain names. This offer includes all the technologies usually used to create professional websites: PHP, MySQL, FTP and SSH access, SSL certificates and easy installation of WordPress or common CMS, etc. It is also possible to add a Node.js site and/or Site Creator.

3. Cloud Server

Professional Web Hosting

With a Cloud Server,the resources allocated to you are not shared with other customersand you can customize the hardware and software configuration of your server according to your needs. A Cloud Server also allows you to use components that are not available on shared web hosting (Node.js, mongoDB, Sol, FFMPEG, etc.).

• A Cloud Server allows you to easily manage your server via the same administration interface as your web hosting – you manage websites in the same way.
• A VPS allows you to manage your server 100% independently with the Windows version or the Linux distribution of your choice (Debian, Ubuntu, openSUSE, ...) – solid technical skills are required to use a VPS, including VPS Lite.

4. Public Cloud (et Kubernetes Service)

Open, reliable, and secure IaaS solution

For Infomaniak, this is the infrastructure that powers kDrive, Swiss Backup, and Webmail, services used by several million users. But Public Cloud is accessible to everyone and provides the resources you need to develop your projects.

With our custom and tailored offers, you'll have no trouble managing your development budget. No setup fees. No minimum amount. Cancel anytime. You only pay for the resources you actually use with Public Cloud at the end of each month, the same applies to Kubernetes Service.

5. Jelastic Cloud

Custom web hosting with the technologies of your choice

Jelastic Cloud allows you to create custom development environments with the technologies of your choice (PHP, Java, Docker, Ruby, etc.). It is a flexible cloud offering:

• Horizontal and vertical resizing of resources.
• Payment based on actual resource consumption.
• Easy customization of your infrastructure (redundancy, IP, SSL, load balancing, etc.).

This guide is intended for users who have their own Windows Server Evaluation version image in Windows Server Standard or Datacenter with a license on Public Cloud.

Introduction

• As a Microsoft partner, Infomaniak provides and automatically bills Windows Server licenses to customers who use instances with these operating systems, standard or datacenter versions.
• Infomaniak offers ready-to-use images for Public Cloud, pre-activated with a license; if activation fails, please refer to this other guide.

Using Your Own Windows Server Image

If you decide to upload your own standard or datacenter Windows Server image, you must follow the activation procedure.

180-day trial version

In the case of a 180-day trial version, you must precede the above procedure with a few additional commands:

Open a command prompt (cmd.exe) via the Start menu, and run the following as an administrator to switch to…

• … Windows Server 2019 standard:
  dism /online /set-edition:serverstandard /productkey:N69G4-B89J2-4G8F4-WWYCC-J464C /accepteula
• … Windows Server 2019 datacenter:
  dism /online /set-edition:serverdatacenter /productkey:WMDGN-G9PQG-XVVXX-R3X43-63DFG /accepteula
• … Windows Server 2022 standard:
  dism /online /set-edition:serverStandard /productkey:VDYBN-27WPP-V4HQT-9VMD4-VMK7H /accepteula
• … Windows Server 2022 datacenter:
  dism /online /set-edition:ServerDatacenter /productkey:WX4NM-KYWYW-QJJR4-XV3QB-6VM33 /accepteula
• … Windows Server 2025 standard:
  dism /online /set-edition:serverstandard /productkey:TVRH6-WHNXV-R9WG3-9XRFY-MY832 /accepteula
• … Windows Server 2025 datacenter:
  dism /online /set-edition:serverdatacenter /productkey:D764K-2NDRG-47T6Q-P8T8W-YP6DF /accepteula

Once the command is complete, restart the instance and follow the standard activation procedure as described in the corresponding FAQ.

This guide explains how to manage users for your Public Cloud project.

Introduction

• To access a project's resources, you need to create OpenStack users (see below).
• These OpenStack users are not related to Infomaniak Manager users.
• The user's username is generated automatically and is provided after its creation.
• These OpenStack users are linked to a project, so they cannot access multiple projects.
• All operations on users (adding, modifying, deleting, etc.) are asynchronous and may sometimes take several minutes to complete.

Create a user for your Public Cloud

To create an OpenStack user after ordering your Public Cloud:

1. Click here to access your product management interface on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question:
   
3. Create a new Project:
   
4. The user defined when creating your project will be in the format PCU-XXXX, and you can assign a description to it for ease of use.

User Password Management

The OpenStack user password can be set immediately upon creation, or it can be generated later using a link that is sent by email to the address of your choice.

To change it later:

1. Click here to access the management interface for your product in the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Manage in the Users column of the project in question:
   
4. Click on the menu to the right of the user in question to access the password change option.

Add a new user to a project

To add more users to your project:

1. Click here to access your product management interface in the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Manage in the Users column of the project in question.
4. Click on Add OpenStack access:
   

Delete a user

To delete an existing user:

1. Click here to access your product management in the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product in question.
3. Click on Manage in the Users column of the project in question.
4. Click on the menu to the right of the user you want to delete:
   

Learn more

• Getting Started Guide: Public Cloud
• Public Cloud: Taking Action on an Existing Project
• Complete product documentation: https://docs.infomaniak.cloud

This guide presents Infomaniak's Public Cloud offering, an Infrastructure as a Service (IaaS) solution based on OpenStack that provides the resources you need to develop your projects.

Introduction

• Infomaniak's Public Cloud, a platform powered by the open-source OpenStack technology, offers virtual instances with several performance profiles:
  • IOPS-optimized instances
  • RAM-optimized instances
  • Instances with the latest generation GPUs
• Range of tools available:
  • Object storage (compatible with S3)
  • Managed Kubernetes service
  • Managed databases
  • Load balancers
  • DNS management
  • Private network services
• Numerous integrations, including:
  • A unified API
  • A Terraform/OpenTofu connector
  • An Ansible collection
• The infrastructure is available in multiple regions in Switzerland, with several availability zones.

Getting started

• The Infomaniak Public Cloud user guide provides numerous tutorials, step-by-step guides, and best practices.
• You can also access all Public Cloud FAQs, including:
  • Create a new project
  • Take action on an existing project
• The list of scheduled maintenance and current issues can be found at https://status.infomaniak.cloud/.
• Discover the Public Cloud presentation (replay of the Infomaniak 2022 Webinar):
  
  
   
  • Understand simply what a Public Cloud (IaaS) is, its uses, and who it is for
  • Complete tutorial for deploying WordPress with OpenStack in Infomaniak Public Cloud (scripts included)
  • Frequently asked questions about Infomaniak Public Cloud (2022)

Pricing

• How billing works
• Estimate the cost of resources used

Community forum & Feedback

• Click here to share feedback or suggestions about an Infomaniak product.
• Access the Reddit page created to facilitate technical discussions with the user community.

This guide explains how to navigate the Public Cloud interface from the Infomaniak Manager and presents the different limits of this service.

Discovering Public Cloud

The list of scheduled maintenance and current issues can be found at https://status.infomaniak.cloud/.

To access the homepage of your Public Cloud:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. You arrive on a page where all the Public Clouds you have ordered are listed:
   1. This button allows you to order a new Public Cloud.
   2. This link allows you to access the comparison page of the different subscription formulas for Public Cloud.
   3. This button allows you to switch from a list or thumbnail view.
   4. Click on the action menu ⋮ to the right of the concerned object to access the options:
      1. The pencil icon ✎ allows you to rename your Public Cloud
      2. The tree icon allows you to access the projects page linked to the selected Public Cloud
3. From this projects page linked to the Public Cloud, you will have access to all your projects:
   1. This button allows you to create a new project that will be linked to the Public Cloud.
   2. This button allows you to switch from a list or thumbnail view.
   3. Click on the action menu ⋮ to the right of the concerned object to access the options:
      1. The first element allows you to access the dashboard of the project
      2. The pencil icon ✎ allows you to rename your project
      3. The right arrow icon allows you to access the OpenStack Horizon dashboard directly.

Additional options are accessible from the left sidebar and under Manage:

Public Cloud Limits

By default, the resources that can be used in a project are limited (for security reasons - to avoid ending up with a high bill at the end of the month, for example).

Learn about the 3 levels of limits detailed in this other guide.

The Manager indicates the limit level assigned to the Organization:


To increase the project limits, contact Infomaniak support.

The limits apply to all projects in the Organization. In an Organization with 5 projects, including 1 that requires level 3, the other 4 projects will inherit a level 3 limit.

This guide explains how to create a new project with Public Cloud Infomaniak.

Prerequisites

• Have read and understood the Getting Started Guide.
• Have Public Cloud on your Infomaniak Manager.

Create a new project

To access Public Cloud:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product on which a new project will be created
   
3. Click the Create a project button:
   
4. Name your project.
5. An OpenStack identifier is automatically created (in the form PCU-XXXX).
6. It is possible to add a description (to specify who the identifier is intended for, for example).
7. Set a password (or send the procedure by email).
8. Click Create to complete the project creation:
   

Resource level

The highest level of resources to which your organization has access is automatically assigned to the project. You can modify it at any time once the project is created.

Also refer to this other guide if you are looking for information about actions on an existing project.

This guide explains the different actions that can be performed from the Manager with Public Cloud.

Access additional options on a project

To access the Public Cloud:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product concerned:
   
3. Click on the Horizon shortcut to connect to it if necessary, or…
4. … click directly on the name of the project concerned to access additional actions:
   
5. You can:
   
   1. rename or delete the project
   2. access the OpenStack Horizon dashboard
   3. manage the billing
   4. access the Kubernetes services
   5. add a new user access
   6. manage the access information of the user concerned:
      1. add or modify the description of the user
      2. modify the password for accessing the project for the user
      3. download configuration files (1 OpenStackRC file or 1 clouds.yaml file) to access your project from the CLI
      4. delete the user from the project

This guide details how billing works for your Infomaniak Public Cloud.

Billing Process

What payment methods are accepted?

You can only pay for Public Cloud service invoices with a credit card.

When is the credit card charged?

The billing period runs from the first day of the month to the last day of the month. The credit card is usually charged on the first day of the following month (depending on your bank, there may be a few days' delay in the charge). An invoice is issued at the time the card is charged.

Are stopped instances billed?

Stopped instances are not billed, except for:

• storage, which continues to use space even if it is unused
• the GPU and IPv4 address of instances placed on a public network

I started an instance for less than an hour; how will I be charged?

Any partial hour is charged.

For example, if an instance is billed at CHF 10 per hour and runs for part of the last hour, CHF 10 will be charged for that hour.

What are Infomaniak ICUs?

Openstack bases its billing on tokens, and therefore the Infomaniak Cloud Unit or ICU was created. This token converts the cost of resource usage on Openstack into CHF or EUR.

ICU to CHF or EUR conversion table:

Learn more

• Getting Started Guide: Public Cloud
• Public Cloud: Performing Actions on an Existing Project
• Complete product documentation: https://docs.infomaniak.cloud

This guide provides some information about Windows licenses for Infomaniak Public Cloud.

Windows license information

As a Microsoft Partner, Infomaniak provides and automatically bills Microsoft licenses for the following operating systems:

• Windows Server 2019 standard and datacenter
• Windows Server 2022 standard and datacenter
• Windows Server 2025 standard and datacenter

Billing is based on the number of VCPU of the instance.

The license belongs to Infomaniak and is not the property of the client. It starts when the client uses one of these versions of Windows Server and stops when the instance is destroyed.

There is no license billing in case of pause or stop of the instance.

Microsoft Partner

• As a Microsoft partner, Infomaniak provides pre-activated corresponding images on Public Cloud, via Horizon or the Openstack CLI.
  • In case of activation failure, refer to this other guide on the subject.
• As a Microsoft partner, Infomaniak does not allow the use of a personal client license (Bring Your Own License); in the case of using its own license, Infomaniak provides and automatically bills the licenses provided by Infomaniak.
  • The client can then activate their OS via the activation procedure.
• As a Microsoft partner, the non-use of licenses (i.e., a 180-day Evaluation version) is also not allowed.
  • These versions are for testing in an internal environment.
  • In the case of using an evaluation version, Infomaniak provides and automatically bills the licenses provided by Infomaniak.
  • The client can then activate their OS via the procedure for converting an evaluation version to a normal activated version.
• If you use Microsoft software within Windows Server that requires a License Mobility, such as Microsoft SQL Server, Microsoft Sharepoint Server, or Microsoft Exchange Server, you must submit the Software Assurance document via the Infomaniak contact form.

This guide covers the creation of private networks between different Infomaniak hosting offers, such as VPS Cloud / VPS Lite, Public Cloud, NAS Synology, etc.

Create a VLAN between VPS

It is recommended to migrate to the Public Cloud offering to create such private networks between VMs.

This guide concerns Public Cloud and the possibility in some cases to increase resources by requesting the activation of certain services.

Prerequisites

• You will be required to provide certain information via kCheck as well as to reload, if necessary, the available credits.

Activate performance levels and special services

In order to obtain the possibility to create instances with a higher performance level and/or specific resources such as the possibility to use instances with GPU, contact the support department of Infomaniak by email specifying the Public Cloud project ID (PCP-XXXXX) and the desired resources.

For example:

I would like to increase the quotas for the PCP-XXXXX project, can you activate resource level 2 and large sizes (XXL).

This guide explains how to recover the password for a Windows image (any version) on Public Cloud.

Connecting to the Windows instance

By default, the username is Administrator.

The password, however, isgenerated during the instance's first boot sequence.

If you are unable to establish the initial connection to your Windows instance, you will need the private key used during the deployment process. Enter this command to install or verify that nova-client is installed:

pip3 install python-novaclient

Then, to retrieve the instance password:

Refer to the official documentation.

Prenez connaissance de la documentation officielle.

You can also check for any ongoing issues on status.infomaniak.com.

Specifically for Public Cloud, the list of scheduled maintenance and ongoing issues can be found at status.infomaniak.cloud.

This guide details the Kubernetes system of Public Cloud that you can order and install directly on your Manager:

Interfaces and pricing of the Infomaniak Kubernetes Service

Infomaniak offers a complete Kubernetes solution with several management interfaces and flexible pricing tailored to your needs.

Available interfaces

The Infomaniak Kubernetes service offers you several methods of access and management:

• Native Kubernetes API: Interact directly with your cluster via the standard Kubernetes API
• Kubeconfig file: Easily configure your command-line tools such as kubectl
• Terraform/OpenTofu: Manage your infrastructure as code (IaC)
• Kubernetes Manager: Intuitive web interface to manage your clusters
• Infomaniak CLI: Automate your operations via command line

Pricing structure

The Infomaniak Kubernetes service offers several plans that correspond to the price of the control plane. It is important to note that resources including network, instances, etc. are not included in this base rate.

The instances necessary for the operation of your applications are billed at the standard rates of Infomaniak's Public Cloud. You automatically benefit from Infomaniak's pricing advantages, including included traffic and low-cost instances, available on the Prices page.

• Instances (VMs): from an amount billed per hour depending on the configuration chosen
• Block Storage: from an amount billed per GB per month
• Snapshot: from an amount billed per GB per month

This structure allows you to pay only for the resources you actually use, while benefiting from a Kubernetes control plane fully managed by Infomaniak.

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.