FR: streamline release overhead

[jkh52]

Currently, releasing a new version tag is cumbersome (https://github.com/kubernetes-sigs/apiserver-network-proxy/blob/master/RELEASE.md).

Manual steps:

• create version tags
• create image promotion PRs
• bump k/k client library and example manifests
  • and backport as appropriate

We should streamline or automate as much as possible.

@ameukam, I briefly discussed this with you and @BenTheElder at KubeCON, I think you had an example of something, automating at least a tag / version step and generating an image promotion PR; do you remember and have any example pattern?

[jkh52]

Initial release (tag) script: #541

[BenTheElder]

I'm not aware of anyone automating promoting PRs yet, but I think it's a good idea if done carefully (the point of promotion PRs is to ensure changes to prod are vetted to have come from a secure and expected build process, in practice how much that helps aside from two-people to merge is down to how your project operates).

[k8s-triage-robot]

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

This bot triages un-triaged issues 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:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale