Repair the workload cluster certificates by manually rotating the token and then restart the KMS plug-in and container. Repair the mocctl certificates by running Repair-MocLogin. Repair the management cluster certificate by manually rotating the token and then restart the KMS plug-in and container. To resolve this issue, run the following steps: If the cluster is rebooted after this period, it will continue to remain in a non-functional state. The cluster is still functional, however, since it's beyond 60 days, you need to call Microsoft support to upgrade. When an AKS on Azure Stack HCI cluster is not upgraded within 60 days, the KMS plug-in token and the certificates both expire within the 60 days. If you don't use a management or workload cluster for longer than 60 days, the certificates expire, and you must renew them before you can upgrade AKS on Azure Stack HCI. If a management or workload cluster is not used for more than 60 days, the certificates will expire To repair the certificates, run the following Repair-AksHciClusterCerts command: Repair-AksHciClusterCerts -Name -fixKubeletCredentials To restart the cluster, you need to manually repair the certificates before you can perform any cluster operations. The certificates expire because they're rotated every 3-4 days for security reasons. When you shut down a management or workload cluster for more than four days, the certificates expire and the cluster is unreachable. If a cluster is shut down for more than four days, the cluster will be unreachable You can also review known issues with Windows Admin Center and installation issues and errors. 
This article describes some common known issues with Azure Kubernetes Service on Azure Stack HCI.
0 kommentar(er)
