Upload release notes JSON (relnotes.k8s.io) to a Google Cloud Bucket

[saschagrunert]

What would you like to be added:

We currently vendor the JSON based release notes for relnotes.k8s.io into the repository:
https://github.com/kubernetes-sigs/release-notes/tree/master/src/assets

We could put these assets on a Google Cloud Storage Bucket to give the Release Notes Team a faster way to update the data as well as avoid having the need for an additional PR on update.

Why is this needed:

It's not necessarily needed, but would improve the workflow around the notes and reduce the complexity.

/cc @cartyc @JamesLaverack @justaugustus

[justaugustus]

/assign
/priority important-soon

I need to noodle on this a little, since it will involve granting more people access to GCP...

[cartyc]

@justaugustus Is this something that could be delegated to a service account or would that too broad and not be granular enough?

[JamesLaverack]

This affects the implementation of krel release-notes (see https://github.com/kubernetes/release/blob/master/cmd/krel/cmd/release_notes.go).

@puerco and I were thinking about the implementation, and we realised that in the existing flow we run release-notes, then run a JS based prettier for the JSON, then PR into k-sigs/release-notes. (See the role handbook for more details). We have to run the prettier (there's a build check on k-sigs/release-notes to make sure you have) and so we'd need to invoke NPM from krel to do this currently. So uploading to a bucket would probably make this easier. (We can still pretty-print the JSON, but we can do that in Go instead of invoking the NPM one).

[saschagrunert]

This affects the implementation of krel release-notes (see https://github.com/kubernetes/release/blob/master/cmd/krel/cmd/release_notes.go).

@puerco and I were thinking about the implementation, and we realised that in the existing flow we run release-notes, then run a JS based prettier for the JSON, then PR into k-sigs/release-notes. (See the role handbook for more details). We have to run the prettier (there's a build check on k-sigs/release-notes to make sure you have) and so we'd need to invoke NPM from krel to do this currently. So uploading to a bucket would probably make this easier. (We can still pretty-print the JSON, but we can do that in Go instead of invoking the NPM one).

Sounds good to me! Sure the prettier-invocation would go away if the website fetches the sources from a remote location. 👍

[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