lib/release: Skip attempts to set GCS object policy on new buckets

[justaugustus]

New Kubernetes infra buckets, like k8s-staging-release-test, have a
bucket-only ACL policy set, which means attempting to set the ACL on an
object will fail. We should skip this ACL change in those instances, as
new buckets already default to being publicly readable.

(There will likely by other places to fix this in the future, but I'd like to do this incrementally to make sure we investigate any permissions errors.)

Ref: https://cloud.google.com/storage/docs/bucket-policy-only
Fixes: #904

Signed-off-by: Stephen Augustus [email protected]

/assign @dims @thockin @tpepper
cc: @kubernetes/release-engineering
/milestone v1.17
/priority important-soon
/kind bug

[k8s-ci-robot]

@justaugustus: Adding label: do-not-merge/blocked-paths because PR changes a protected file.

Reasons for blocking this PR:

[Changes to certain release tools can affect our ability to test, build, and release Kubernetes. This PR must be explicitly approved by SIG Release repo admins.]

• lib/releaselib.sh

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.

[dims]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [justaugustus]

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