kubernetes：无法更新端点警告
kubernetes: Failed to update endpoints warning
这是我在 kubectl get events 输出中注意到的一些东西
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 资源
我注意到在图像更新期间出现了一些小的服务不可用问题，因此我正在尝试检查这是否相关。
在 istio.
之上，在主节点和节点上使用版本 v1.12.7-gke.25 的 GKE
k8s 的常见行为是让 k8s 客户端（控制器）知道重试。
Kubernetes leverages the concept of resource versions to achieve optimistic concurrency. concurrency-control-and-consistency
由系统填充。
To enable clients to build a model of the current state of a cluster, all Kubernetes object resource types are required to support consistent lists and an incremental change notification feed called a watch. Every Kubernetes object has a resourceVersion field representing the version of that resource as stored in the underlying database. When retrieving a collection of resources (either namespace or cluster scoped), the response from the server will contain a resourceVersion value that can be used to initiate a watch against the server. The server will return all changes (creates, deletes, and updates) that occur after the supplied resourceVersion. This allows a client to fetch the current state and then watch for changes without missing any updates. If the client watch is disconnected they can restart a new watch from the last returned resourceVersion, or perform a new collection request and begin again efficient-detection-of-changes
这是我在 kubectl get events 输出中注意到的一些东西
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 资源
我注意到在图像更新期间出现了一些小的服务不可用问题，因此我正在尝试检查这是否相关。
在 istio.
v1.12.7-gke.25 的 GKE
k8s 的常见行为是让 k8s 客户端（控制器）知道重试。
Kubernetes leverages the concept of resource versions to achieve optimistic concurrency. concurrency-control-and-consistency
由系统填充。
To enable clients to build a model of the current state of a cluster, all Kubernetes object resource types are required to support consistent lists and an incremental change notification feed called a watch. Every Kubernetes object has a resourceVersion field representing the version of that resource as stored in the underlying database. When retrieving a collection of resources (either namespace or cluster scoped), the response from the server will contain a resourceVersion value that can be used to initiate a watch against the server. The server will return all changes (creates, deletes, and updates) that occur after the supplied resourceVersion. This allows a client to fetch the current state and then watch for changes without missing any updates. If the client watch is disconnected they can restart a new watch from the last returned resourceVersion, or perform a new collection request and begin again efficient-detection-of-changes