Disable stalebot in ingress-nginx

[rikatz]

We are under a lot of heavy work. This doesn't mean we don't care for issues and PRs, but more that we couldn't check all the reports yet.

We need to do a better job, I know :) we all are contributors and do this for free. This doesn't mean we need to close issues and PRs because we couldn't even triage those.

So based on my experience as a contributor and how upset I get when I have to keep doing lifecycle active commands, I'm proposing that we remove the stale bot (as KinD and @BenTheElder did) so we don't simply close issues and PRs.

Based on this, and if accepted by other contributors, we have an agreement we need to start taking better care on PRs and issues, even at least saying to the user "ack, we are under heavy work but we understand that this is important to you and wont be automatically closed".

/cc @strongjz @tao12345666333 @ElvinEfendi

[k8s-ci-robot]

@rikatz: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-test-infra-prow-checkconfig-beta	3b5e860	link	false	/test pull-test-infra-prow-checkconfig-beta

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[rikatz]

/hold
For discussion in our weekly community meeting

[BenTheElder]

/approve

FWIW I've found this leads to less duplicate issues and more realistic issue counts, but it does mean manually opting to close out inactive support tickets.

I personally find that trade-off acceptable.

There's no particular rush to close issues that aren't labeled urgent and aren't receiving activity, but it is something you get a poor approximation of with no human effort from the bot. Notably on the other hand the bot cannot distinguish this from issues that simply aren't being worked on yet and therefore have nothing to add besides users politely adding +1 reactions that do not alter the timestamp and will not prevent closure.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, rikatz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/sig-k8s-infra/trusted/OWNERS [BenTheElder]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tao12345666333]

One of my previous ideas was to have the bot filter by adding a specific label . But considering our actual situation, this may not be appropriate

[strongjz]

In our community meeting today, we discussed having @cpanato update the bot so we can only label issues as stale and not close them.

This will help us track them but not close them.

[BenTheElder]

To label without closing you only need to opt out of the close query, except then it will post a misleading comment when labeling them.

So instead all the jobs except the close job will need to be duplicated with new comments written 😅

Should not require code changes.

[cpanato]

so we just need to opt-out from the ci-k8s-triage-robot-close job if i get that right

@BenTheElder @rikatz @strongjz

[BenTheElder]

Yeah though if you do that when it labels the issues it will post the same comment it uses everywhere else which tells people that it will be auto closing it

[cpanato]

@rikatz @strongjz if you dont want that we can drop everything and then have a gtihub action to label things for us with custom text and not close it

[BenTheElder]

The robot commenter is general. The text is configured in the jobs (expand the diff).
It's just not configured on a per repo basis.

So instead all the jobs except the close job will need to be duplicated with new comments written 😅

[k8s-triage-robot]

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/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was 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

[cpanato]

ok, as we discussed we will disable the stale bot for now.

/lgtm
/unhold to continue the work

[cpanato]

/hold cancel

[k8s-ci-robot]

@rikatz: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key sig-contribex-k8s-triage-robot.yaml using file config/jobs/kubernetes/sig-k8s-infra/trusted/sig-contribex-k8s-triage-robot.yaml

In response to this:

We are under a lot of heavy work. This doesn't mean we don't care for issues and PRs, but more that we couldn't check all the reports yet.

We need to do a better job, I know :) we all are contributors and do this for free. This doesn't mean we need to close issues and PRs because we couldn't even triage those.

So based on my experience as a contributor and how upset I get when I have to keep doing lifecycle active commands, I'm proposing that we remove the stale bot (as KinD and @BenTheElder did) so we don't simply close issues and PRs.

Based on this, and if accepted by other contributors, we have an agreement we need to start taking better care on PRs and issues, even at least saying to the user "ack, we are under heavy work but we understand that this is important to you and wont be automatically closed".

/cc @strongjz @tao12345666333 @ElvinEfendi

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.