Update audit

[spiffxp]

I would not recommend trying to review all files at once.

This was primarily intended to pick up everything from #830 (prow build clusters and related infra), and demonstrate that #806 (prototype prow build cluster) has nothing hanging around (most of which was picked up from unmerged audit #807)

This picks up:

• Stripped out fingerprint properties from audit #810 - strip fingerprint from project-info
• add prow build clusters #830 (part) - give gcb-builder service account
• legacy bucket writer stuff?
• Use gcloud secrets instead of git-crypt for groups #821 - use secrets for groups reconciler
• Added staging repository for infra-tools #805 - add k8s-staging-infra-tools
• Prepared slack-infra registry namespace #802 - add k8s-staging-slack-infra
• Turn down kubernetes-public/development2 cluster #785 - turn down development2 cluster
• add prow build clusters #830 (part) - add k8s-infra-prow-build project / cluster / service accounts
• add prow build clusters #830 (part) - add k8s-infra-prow-build-trusted project / cluster / service accounts
• add prow build clusters #830 (part) - add k8s-infra-e2e-* projects
• refresh kubernetes-public ssh keys (part of removing dev2 cluster, part of a mea culpa from Update audit as of 2020-04-27 #807)
• Add a k8s-infra-gcp-auditor service account #804 - add k8s-infra-gcp-auditor service account
• Add infra scripts/terraform for prow build cluster prototype #806 - add kubernetes-public/prow-build-test cluster

and then two commits at the end where I'm not entirely sure what happened

[spiffxp]

/cc @thockin

[thockin]

This was @dims. It's sadly easy to enable just by clicking the UI wrong. Not harmful, but I manually reverted this anyway.

We need Hourly runs of audit and PRs :)

[dims]

whoa! Sorry again

[thockin]

The legacy bucket writer stuff is odd. Activity shows it was you on April 30, 2020 at 10:20:48 PM GMT-7

[dims]

Glad we have this to keep us honest! :)

[spiffxp]

@thockin

The legacy bucket writer stuff is odd. Activity shows it was you on April 30, 2020 at 10:20:48 PM GMT-7

I don't have the history to prove when I ran it, but I suspect I ran ./ensure-staging-storage.sh to hit all buckets, and this was likely after some refactoring you had done (I just couldn't identify the PR)

[spiffxp]

Are we fine merging this as is and having a followup audit catch us cleaning up?

[dims]

Sounds good @spiffxp !

[dims]

/approve
/lgtm

/hold for @thockin

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, spiffxp

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:

• OWNERS [dims,spiffxp]

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

[spiffxp]

/hold cancel
(spoke with @thockin offline)