The MSI certificate used for this cluster has expired. Features such as configuration, monitoring, and more will not work until the resource and agents have been recreated.

Virender Singh Rawat 67 Reputation points
2023-08-21T06:32:23.2266667+00:00

We have configured AKS on top of azure stack HCI. it was configured successfully 6 months back but today, we are getting below error.

The MSI certificate used for this cluster has expired. Features such as configuration, monitoring, and more will not work until the resource and agents have been recreated.

Can you help to fix this issue like command or steps which need to follow.

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
342 questions
Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,103 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Trent Helms - MSFT 2,541 Reputation points Microsoft Employee
    2023-08-21T14:07:05.4166667+00:00

    Hi Virender,

    The MSI certs are valid for a period of 90 days and should auto-renew within 45 days to stay up-to-date. I would investigate why the cluster was disconnected for so long that it could not auto-renew the cert.

    To fix this issue, it is my understanding that you must delete and reconnect the cluster so the cluster can get a new certificate. Below is an example of the commands that can be used for this purpose.

    NOTE: The commands below are provided as-is with no warranties or guarantees of support. It is up to you as the user to verify and test the commands thoroughly. Microsoft accepts no liability from the use of these commands in any form. If you are not comfortable with testing these commands, you can open a support request with Microsoft where we can assist you further.

    1. Delete the current connectedcluster installation using az connectedk8s delete -n <CC Name> -g <RG Name>
    2. Connect the cluster once again using az connectedk8s connect -n <New CC Name> -g <New RG name>

    Hope this helps!

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.