Provide links to k8s control plane images

[b10s]

What would you like to be added:

Would be great to add links to images with official k8s control plane binaries to release notes/changelog

Why is this needed:

Some users do deploy k8s using their own way without kubeadm.

They'd better have link to images instead using binaries to stick to best practice:
binary kubelet + other control plane parts as containers

[justaugustus]

/assign @saschagrunert @puerco

[saschagrunert]

From a technical perspective I think we could add a new flag to krel changelog to provide the release --images path. This path can be used to implement something like:

release/lib/releaselib.sh

Lines 1052 to 1078 in 8c711b5

	for arch in "${arches[@]}"; do
	for tarfile in $release_images/$arch/*.tar; do
	# There may be multiple tags; just get the first
	orig_tag=$(tar xf $tarfile manifest.json -O | jq -r '.[0].RepoTags[0]')
	if [[ ! "$orig_tag" =~ ^.+/(.+):.+$ ]]; then
	logecho "$FAILED: malformed tag in $tarfile:"
	logecho $orig_tag
	return 1
	fi
	binary=${BASH_REMATCH[1]}
	new_tag="$push_registry/${binary/-$arch/}"
	new_tag_with_arch=("$new_tag-$arch:$version")
	manifest_images["${new_tag}"]+=" $arch"
	logrun docker load -qi $tarfile
	logrun docker tag $orig_tag ${new_tag_with_arch}
	logecho -n "Pushing ${new_tag_with_arch}: "
	# TODO: Use docker direct when fixed later
	#logrun -r 5 -s docker push "${new_tag_with_arch}" || return 1
	logrun -r 5 -s $GCLOUD docker -- push "${new_tag_with_arch}" || return 1
	if [[ "${PURGE_IMAGES:-yes}" == "yes" ]] ; then
	logrun docker rmi $orig_tag ${new_tag_with_arch} || true
	fi
	done
	done

The same logic would be needed when converting parts of anago to a golang based version.

[puerco]

I can take it @saschagrunert unless you want to for some particular reason

[saschagrunert]

I can take it @saschagrunert unless you want to for some particular reason

Sounds good, thank you @puerco!

[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

[puerco]

/remove-lifecycle stale

[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

[puerco]

/remove-lifecycle stale

[saschagrunert]

@puerco I assume that this will be resolved with #1837 now.

[puerco]

Yes, it's one of the tasks that should get resolved as a byproduct of the BOM :)

[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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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/test-infra repository.