本文介绍了kubernetes:无法更新端点警告的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
这是我在kubectl get events
输出中看到的东西
Here is something I noticed in my kubectl get events
output
Warning FailedToUpdateEndpoint Endpoints Failed to update endpoint mynamespace/myservice: Operation cannot be fulfilled on endpoints "myservice": the object has been modified; please apply your changes to the latest version and try again
我知道,但由于我没有通过yaml
显式创建Endpoint
资源,因此我认为这并不适用.
I am aware of this discussion, but I do not think is applicable, given I am not explicitly creating an Endpoint
resource via yaml
.
在图像更新过程中,我注意到一些次要的服务不可用,所以我试图检查是否与此有关.
I am noticing some minor service unavailability during image updates so I am trying to check if this is related.
在主服务器和节点上都在istio
的顶部上使用版本为v1.12.7-gke.25
的GKE.
Using GKE with version v1.12.7-gke.25
on both masters and nodes, on top of istio
.
推荐答案
k8s 的常见行为是让k8s客户端(控制器)知道再试一次.
It's common behaviour of k8s to let the k8s clients (Controllers) know to try again.
由系统填充.
这篇关于kubernetes:无法更新端点警告的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!