Reinstate aws-janitor

[justinsb]

In particular, stop exiting with a non-zero exit code when we cleaned
up some resources.

That's not an error; this is the janitor doing what it is supposed
to. It makes it look like the janitor is failing, when in fact another
job is leaking resources.

[chases2]

/lgtm
/lint

[k8s-ci-robot]

@chases2: 0 warnings.

In response to this:

/lgtm
/lint

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.

[BenTheElder]

/cc @amwat

[BenTheElder]

/approve
/hold

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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/OWNERS [BenTheElder]
• maintenance/aws-janitor/OWNERS [BenTheElder,justinsb]

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

[BenTheElder]

/cc @detiber

[detiber]

/lgtm
/hold cancel

[k8s-ci-robot]

@justinsb: Updated the job-config configmap in namespace default using the following files:

• key janitors.yaml using file config/jobs/kubernetes/test-infra/janitors.yaml

In response to this:

In particular, stop exiting with a non-zero exit code when we cleaned
up some resources.

That's not an error; this is the janitor doing what it is supposed
to. It makes it look like the janitor is failing, when in fact another
job is leaking resources.

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.