Base release milestone generation/updates for schedule.md and GCal entries on yaml data

[dhiller]

Is your feature request related to a problem? Please describe:

/sig release
/priority backlog

In a kubevirt-dev thread we discussed that we want to have the release milestones added to the KubeVirt Google Calendar.

It was suggested to capture the milestones in a yaml and generate the schedule.md from this yaml. In a second step we could also generate the milestone entries in GCal from this. With two prowjobs we could keep both documents in sync whenever the yaml source changes.

Describe the solution you'd like:

Plan:

• create a yaml file containing the data from a current schedul
• create a generator that creates the schedule.md
• create a prowjob that calls the generator on updates of the yaml
• create a generator that creates/updates the release milestones in GCal (requires a secret in the cluster to access the GCal)
• add secret to the cluster secrets, deploy it in the usual way
• create a prowjob that updates the release milestones on updates of the yaml

Describe alternatives you've considered:
Manual creation/update of the release milestones will work in the meantime :)

Additional context:
Example: creation of GitHub secret in project-infra

[fossedihelm]

A possible starting point could be: https://github.com/kubernetes/release/tree/master/cmd/schedule-builder

[dhiller]

A possible starting point could be: kubernetes/release@master/cmd/schedule-builder

@fossedihelm thanks for the heads up, looks interesting! However IIUC it doesn't do what we want to tackle - creating GCal items - or did I overlook it?

[fossedihelm]

@dhiller Yes, it was just a report to take a cue maybe :)