migrate maintenance-pull-janitor to pod-utils

[jbpratt]

Signed-off-by: jbpratt [email protected]

Ref. #17719 and #20760
/kind cleanup
/area jobs
/area bootstrap
/area prow/pod-utils
/sig testing
/cc @dims

update maintenance-pull-janitor to pod-utils following https://gist.github.com/dims/c1296f8ed42238baea0a5fcae45f4cf4

[k8s-ci-robot]

@jbpratt: The label(s) area/prow/pod-utils cannot be applied, because the repository doesn't have them.

In response to this:

Signed-off-by: jbpratt [email protected]

Ref. #17719 and #20760
/kind cleanup
/area jobs
/area bootstrap
/area prow/pod-utils
/sig testing
/cc @dims

update maintenance-pull-janitor to pod-utils following https://gist.github.com/dims/c1296f8ed42238baea0a5fcae45f4cf4

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.

[k8s-ci-robot]

Hi @jbpratt. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jbpratt
Once this PR has been reviewed and has the lgtm label, please assign cblecker for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• config/OWNERS

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

[BenTheElder]

this command doesn't do much on its own (wraps actual test command with things like setting up docker in docker if need be)
still need to run the "janitor" logic

[jbpratt]

Suggested change

	- runner.sh
	- runner.sh
	- "scenarios/kubernetes_janitor.py"

that is what I was thinking, but I wasn't sure. Would it just be as simple as passing in the current scenario script? like https://gist.github.com/dims/c1296f8ed42238baea0a5fcae45f4cf4#file-after-yaml-L36-L38 or should the scenario script be moved?

[BenTheElder]

I think in the past we've used the scenario file as-is to start.
Sorry, my bandwidth will be very poor for the next few weeks with https://kubernetes.slack.com/archives/CCK68P2Q2/p1679420278418599 / https://kubernetes.io/blog/2023/03/10/image-registry-redirect/

[jbpratt]

updated! No worries, I know you are busy :)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages 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 PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale