KEB release pipeline and Semantic Versioninig

[PK85]

Description

We must provide a GA pipeline to release a new KEB version on the given tag. Then we can use it and bump in the resources directory.

Reason

Better release process than now.

AC

• 1) take all the work we spend to create a release pipeline in the BTP-Manager, like:
  • 1.1) release notes generation
  • 1.2) KEB new labels bug/enha/feature + checking them on PR level (same as in the BTP Manager)
• 2) document new release process
• 3) rethink what kind of tests we use. Right now it is only unit tests. Think about how to test it more in the integration way. Result must be a decision what are the next steps.

Links

• info what SRE is doing around KEB testing: https://github.tools.sap/kyma/management-plane-charts/issues/354

[piotrmiskiewicz]

• test-infra release job(s): Add KEB release job test-infra#9265 (only KEB) KEB jobs release builds test-infra#9292 (jobs)
• KEB yaml as a release artifact - deprecated - not used byt anyone
• sec. scanning config file, sec. scanning bump Create or update sec. scanning config file in the release workflow #176 Add enhancement label to KEB repo test-infra#9349
• labels validation
• unit tests, go mod tidy
• create a release
• waiting for docker images to be built and signed (prow job succeeded) Add commit status check to release workflow #189
• documentation
• define ticket about tests which are missing

[MarekMichali]

• New release label validator
• Add test to render and apply helm charts on k3s. Run on PR and release
• Disable old post-main-build Prow jobs