Kops - Create S3 bucket for hosting CI results

[rifelpet]

Barring a better solution for interacting with both a GCS bucket and the Kops AWS account in one prow job (see kubernetes/kops#16637 (comment)), I'm experimenting with storing Kops' version markers and CI artifacts on S3 instead of GCS, that way the prow jobs only need to interact with one cloud provider.

I will test this with kubernetes/kops#16659 and kubernetes/test-infra#32918

/cc @upodroid @hakman

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rifelpet
Once this PR has been reviewed and has the lgtm label, please assign thockin for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• infra/aws/OWNERS

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

[upodroid]

Instead of doing this, I can fix the rbac issues

[rifelpet]

Ok that works for me too. kubetest2-kops today uses the k8s-staging-kops bucket you introduced here:

The new pull-kops-e2e-k8s-aws-calico-k8s-infra job that runs on the k8s-infra-kops-prow-build prow cluster reports this error:

AccessDeniedException: 403 prow-build@k8s-infra-prow-build.iam.gserviceaccount.com does not have storage.objects.create access to the Google Cloud Storage object. Permission 'storage.objects.create' denied on resource (or it may not exist).

If we can fix that RBAC then we should be able to migrate all presubmit jobs.

If we reuse the k8s-staging-kops bucket for version markers, we just need to update the version markers in our prow jobs to use the new bucket:

https://github.com/kubernetes/test-infra/blob/ff39426505bbbfea5b4a70e9213ffd070bdb5db4/config/jobs/kubernetes/kops/build_jobs.py#L755

Let me know when you've fixed the RBAC and I can continue with this migration work.