Clean up secrets created during the tests.

[dargudear-google]

I am working on-recreating a prow job and these prow jobs deleted during migration to community infra. Discussion ref.

I am re-enabling this job to run on community infra.
To run the job in community infra, I need to create secrets from google secret manager.

This PR is to remove secrets created during the job execution.

[k8s-ci-robot]

Welcome @dargudear-google!

It looks like this is your first PR to kubernetes-sigs/boskos 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/boskos has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @dargudear-google. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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-sigs/prow repository.

[krzyzacy]

does this work locally? could you update the description for your use case?

[krzyzacy]

/ok-to-test

[dargudear-google]

does this work locally? could you update the description for your use case?

Yes. I tried with my personal project and secret cleaning was successful with one related error

Fail to list resource 'topics' from project '<project_id>': ValueError("missing key: creationTimestamp or createTime

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dargudear-google, krzyzacy

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:

• cmd/janitor/OWNERS [krzyzacy]

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

[BenTheElder]

kubernetes/k8s.io#7531 broke Kubernetes CI which reports containing bc478df...445d89e

that appears to solely contain this PR

I think we need to fix and/or revert.

tentatively: it fails because it tries to use the secret manager API even if it's not enabled, leaving the projects stuck in dirty state and causing us to run out of projects.

we need to gracefully handle that the project doesn't have the API enabled and therefore has nothing to clean up.

[BenTheElder]

filed #209 to track next steps.

[krzyzacy]

we probably should revert the deployment first

[BenTheElder]

we probably should revert the deployment first

That's done and CI is green again, I did that first before following up here (kubernetes/test-infra#33910), but we will want to get boskos into a state where updating the deployment is safe.

[dargudear-google]

Here is the PR with API enabled check #211