k8s-triage-robot
commented
2 years ago 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:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
k8s-ci-robot
What would you like to be added: Some sort of basic status for completion of updates.
Why is this needed: Right now I have a helm chart using federated api objects. when using helm --upgrade install, it finishes in 5 seconds because that's how long it takes to update the federated objects, but not for kubefed to actually update all the underlying objects.
for example, kubectl desctibe federateddeployment my-federated-deployment, will not show any indication of an update. There's the Last Transition Time and Last Update TIme timestamps, but they are not updating. I can see the UpdateInCluster event on it, but that doesn't help me since it's not indicating that it's done.
/kind feature