Grant GKE service account "Container Analysis Occurrences Viewer" role

[listx]

It appears that Container Analysis Service is already turned on for k8s-artifacts-prod. But in order to consume this information (e.g., cloud vendors such as GKE), the "Container Analysis Occurrences Viewer" role must be granted to the vendor. For GKE, the service account that needs this role is vulnerability@gke-release-staging.iam.gserviceaccount.com.

/cc @thockin @destijl @simony-gke

[listx]

I think ultimately the PR for this boils down to adding another special-cased grant in infra/gcp/ensure-prod-storage.sh, but I wonder if we need to think about separating permissions tied to vendor-specific needs (third party organizations) to a separate script or separate hierarchical system. AFAIK all of the current grants deal with community groups (such as the artifact admins), not third parties.

[thockin]

I wonder if we can turn that into pub-sub or something less intrusive

[listx]

I wonder if we can turn that into pub-sub or something less intrusive

Do you mean adding a pub-sub layer and letting third parties consume those pub-sub messages (instead of having direct access as Container Analysis Occurrences Viewer)?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.