Closed BenTheElder closed 2 months ago
cc @cpanato
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
/lifecycle frozen this is still super wasteful
/assign
Thanks for raising this @BenTheElder, I've had a go at a fix via #62.
/reopen @jeefy we still need to get this change deployed into k8s infra cc @ameukam less logging costs for k8s infra :+)
@BenTheElder: Reopened this issue.
I don't think we've deployed a new build for 3+ years now https://github.com/kubernetes/k8s.io/blob/main/apps/slack-infra/resources/slack-moderator-words/deployment.yaml
xref: #66
This is actually fixed now.
/assign
This is super wasteful 😱
Right now it's down due to https://github.com/kubernetes/community/issues/6841 so it's not logging at the moment.
We should only log relevant debug info, not every single event processed in full. None of the other tools in this repo do this.