AKS节点配置错误 [英] AKS Node Provisioning Error

查看:128
本文介绍了AKS节点配置错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有一个包含3个节点的AKS集群。在创建部署时,容器和服务崩溃了。在诊断时,其中一个节点显示错误代码 -    VMArtifactRepositoryInternalError,以及网关
超时为"
获取托管群集  AccessProfile  按列表凭据"。 该问题已通过
重新启动节点解决。谁能帮助我知道导致错误的原因?以及如何确保它不会再次发生?

解决方案

我们在这里提到了这个错误: 


https://docs.microsoft.com/en -us / azure / virtual-machines / troubleshooting / error-messages


该文档专门针对虚拟机,但当您的群集在虚拟机上运行时,错误仍然匹配。  ;


基本上,这是一个内部平台错误。通常是短暂的,而不是你可以重现的东西。所以你不需要做任何事情来避免它,它通常不会发生,但无论它是否再次发生,都是由于平台问题没有发生。


We have an AKS cluster with 3 nodes. On creating a deployment the containers and services crashed. On diagnosis one of the nodes was showing errorcode -  VMArtifactRepositoryInternalError , and gateway timeout for "Get Managed Cluster AccessProfile by List Credential".  The issue was solved by restarting the node. Could anyone help me to know what caused the error? And how to ensure it doesn't happen again? 

解决方案

We do mention this error here: 

https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/error-messages

The doc is specifically for VMs but seeing as your cluster runs on a VM the error still matches. 

Essentially, it's a internal platform error. Generally transient and not something you can reproduce. So nothing you need to do to avoid it, it generally does not happen but regardless if it does again, it is due to a platform issue nothing you did. 


这篇关于AKS节点配置错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆