Automate Release process

[dthomson25]

Current the release process includes:

• Create new branch for release or check out the branch
  • Cherry-pick changes into the branch
  • Edit version file and remake manifests
• Create Release notes
• Publish Release
• Upload darwin and Linux versions of controller and kubectl plugin
• Build and publish a new docker image
• Update version/contributing in Master
• Update stable tag
• Post about release

We can automate most of these steps in CircleCI.

[kostis-codefresh]

@dthomson25 I would like to understand better what is the current manual process of creating a release

"Cherry-pick changes into the branch". What changes are exactly chosen? Is the release just what is on the master branch at any given time or something different happens?

Is there a document that explains now how each release happens?

[github-actions]

This issue is stale because it has been open 60 days with no activity.