Add release notes JSON draft

[saschagrunert]

What type of PR is this:

/kind feature

What this PR does / why we need it:

We will use this JSON draft as artifact during the release process,
which allows consumers to get a machine-readable format of the notes.

The notes have been generated via:

> release-notes --format=json \
    --maps-from=$GOPATH/src/k8s.io/sig-release/releases/release-1.20/release-notes/maps \
    --start-rev=v1.19.0 \
    --end-rev=v1.20.0-rc.0

Which issue(s) this PR fixes:

Refers to kubernetes/release#1087 and kubernetes/release#1815

Special notes for your reviewer:

/cc @wilsonehusin @puerco

[hasheddan]

/lgtm
/hold for assignees

[puerco]

Should be fine when paired #1731, that is unless more edits happen in the coming days (but we should have automated this by then)
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hasheddan, puerco, saschagrunert

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:

• releases/release-1.20/OWNERS [hasheddan,saschagrunert]

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

[wilsonehusin]

oh interesting, I didn't know this workflow.

I made edits to the Markdown Draft PR directly on Markdown instead of krel because it was too many to go through sequentially when I already know rhe PR numbers to edit.

I'm guessing this command is running through the map instead of the markdown -- correct? if so, that means this JSON might be missing some entries which I added to Markdown manually 😐

[saschagrunert]

oh interesting, I didn't know this workflow.

Are you referring to the mapping workflow itself? Do we lack documentation about it?

If it was about the JSON file, then this is new and we definitely have to update the docs. I can follow up on that one.

I made edits to the Markdown Draft PR directly on Markdown instead of krel because it was too many to go through sequentially when I already know rhe PR numbers to edit.

I'm guessing this command is running through the map instead of the markdown -- correct? if so, that means this JSON might be missing some entries which I added to Markdown manually 😐

We always had a gap between the manually edited release notes and the generated JSON in the past, so I guess it’s fine. In the future we can use the maps to synchronize both versions directly.

[wilsonehusin]

Are you referring to the mapping workflow itself? Do we lack documentation about it?

JSON file 😄

We always had a gap between the manually edited release notes and the generated JSON in the past, so I guess it’s fine. In the future we can use the maps to synchronize both versions directly.

gotcha! LGTM

/hold cancel

[wilsonehusin]

for the record, these are the missing notes which I manually added to #1371

• dual stack services kubernetes#91824
• refactor(apiserver): disable insecure port kubernetes#95856
• make flags of TokenRequest required kubernetes#95896
• kubeadm: make "alpha kubeconfig user" accept --config kubernetes#94879
• make flags of TokenRequest required kubernetes#95896