Automated release process for KIM

[tobiscr]

Description

The creation of a KIM release is currently a semi-automated process which is time consuming and potentially failure prone.

Goal is to establish a nearly fully automated release process (e.g. by using Github Actions) which covers these steps:

• Define the semantic version for the release and the Github commit + container images we want to release
• Generate / collet the test report for the released sources
• Create a Github release which includes following artefacts:
  • Test report
  • Change log between the previously and currently released version
• Tag the Github revision using its semantic version
• Tag the container images with the semantic version
• Create a PR which triggers the SRE Argo-CI release mechanism

AC:

• Align with other teams (@kyma-project/gopher , @kyma-project/jellyfish , Tunas) how their release process works
• Verify if it would be helpful to move the KIM sources to the SAP Github to simplify the release process and share the results with the team
• Ensure a release can be created by a single action
• The release process enforces a semantic versioning
• Commit in Github and the released container images are tagged with this semantic version
• A Github release is produced which includes the test-results as artefact (can be used as evidence for the SAP microdelivery)
• Rollout to the target KCP environment is triggered

Reasons

Automated release process to reduce time efforts and reduce risk of manual mistakes.

Attachments

Relates to
kyma-project/application-connector-manager#104