Open karlkfi opened 2 years ago
The main client causing drift right now is the Config Sync resource-group-controller, which updates the ResourceGroup (inventory) status.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten /lifecycle frozen
Right now, inventory updates may return a conflict error from Kubernetes. The inventory client should detect this (
apierrors.IsConflict(err)
) and retry with a new Get (to update the ResourceVersion) + Update.Example retry code:
example usage:
Another option is to use https://github.com/flowchartsman/retry which is nice and generic. gcloud and client-go also have retry libs.