Requesting to Enable CORS on gcsweb.k8s.io for easy access via AJAX calls to bucket objects

[ashnehete]

On relnotes.k8s.io we want to fetch the release notes for each release directly from the bucket using a AJAX call. Relevant issue: kubernetes/release#1087

While trying to fetch the object using a gcsweb.k8s.io link (eg. https://gcsweb.k8s.io/gcs/kubernetes-release/release/release-notes-index.json) we ran into a CORS error. It seems that CORS isn't enabled on the GCS bucket.

Will it be possible to enable CORS on the bucket?

/cc @saschagrunert

[saschagrunert]

@spiffxp @dims @justaugustus do you think that we could set the CORS config for the kubernetes-release bucket?

Like:

[
  {
    "AllowedHeaders": ["*"],
    "AllowedMethods": ["GET"],
    "AllowedOrigins": ["https://relnotes.k8s.io/"]
  }
]

[dims]

@saschagrunert Is this script-able?

[saschagrunert]

@saschagrunert Is this script-able?

Yes, gsutil has a cors subcommand:

> gsutil cors set JSON_FILE_NAME.json gs://BUCKET_NAME

[ashnehete]

I just had a thought, do we want to restrict AllowedOrigins to only https://relnotes.k8s.io/ or open it up for everyone (*)? This will make the testing easier on localhost as well as open up avenues for other tools to use the objects in the bucket programmatically. Only downside I see is the security implication.

[spiffxp]

/assign @listx
gs://kubernetes-release lives in a project I do not have rights to edit or modify in any way (ref: #1571), so it's not clear to me whether we can accommodate this request

It could be that fully migrating to gs://k8s-release is a blocker to this (the first step / proof-of-concept for doing so being #1569)

[listx]

The gs://kubernetes-release lives in the google-containers GCP project, and I also do not have rights to modify it. Fully migrating to k8s-release seems to be the right thing.

[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-contributor-experience at kubernetes/community.
/lifecycle stale

[spiffxp]

/remove-lifecycle stale

[spiffxp]

/milestone v1.23
This is going to have to wait until we can move the project to gs://k8s-release

[spiffxp]

/priority backlog

[ameukam]

/milestone clear
/lifecycle frozen

[ameukam]

I think this is solved. Otherwise feel free to open a new issue.

/close

[k8s-ci-robot]

@ameukam: Closing this issue.

In response to this:

I think this is solved. Otherwise feel free to open a new issue.

/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-sigs/prow repository.