fix:Kubernetes registry get k8s pod list #2173
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When kubernetes is deleting a pod,it will first update the metadate of the pod object and add "Deletiontimestamp" field。But at this time, the action received by the watch at this time is update.which will result in untimely service discovery.I think at this time, you can delete the pod and judge that if the metadate of the pod has the deletiontimestamp field,the pod is not available by default.
This is my opinion. Please code review.