audit followup: give k8s-conform serviceaccounts objectAdmin privileges for their respective gcs buckets #1850
Labels
area/audit
Audit of project resources, audit followup issues, code in audit/
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Milestone
Followup for https://github.com/kubernetes/k8s.io/pull/1800/files#r597514009
Currently we give humans (
group:k8s-infra-conform-foo
)roles/storage.objectAdmin
for the gcs bucketk8s-conform-foo
, but the corresponding service account only getsroles/storage.objectCreator
I believe this was chosen at the time to ensure rogue automation couldn't go delete a bunch of results. But I'm fine giving it the more elevated privileges we extend to humans. The use case motivating this is allowing CI using that serviceaccount to update well-known files within the bucket (version-marker, latest build, etc.)
The text was updated successfully, but these errors were encountered: