KEB: Add new/adjust GitAction job that tests if we can install chart by helm

[PK85]

Reason

Already happen twice that KEB release was green, and then in the environment some pods were failing because of missing configuration.

AC

• [ ] 1) We should fail if code requires some env and chart is not providing them
• [ ] 2) All jobs that use gcloud proxy are running and properly closed (without error or forever processing)

Ideas

• [ ] 1) Extends this guy https://github.com/kyma-project/kyma-environment-broker/blob/main/.github/workflows/run-keb-chart-tests-reusable.yaml to do helm install too.
• [ ] 2) Use initialization.yaml from Maper (check with him)
• [ ] 3) Helm release must be OK ( internally helm check if all deployments, jobs are created and deployed without issues). Consider not including jobs to be installed, cause they could fail beacause they cannot reach some APIs like CIS. That means we will check deployments, keb and subaccount-sync.
  • [ ] 3.1) maybe we need flag for all jobs that indicates onlu configuration testing, without executing main job code (configuration ConsistencyCheck)
  • [ ] 3.2) will be nice to somehow test schema-migrator, but for that we need local postgress

[jaroslaw-pieszka]

Ad 1. If we want to use helm install instead of helm template . | kubectl apply -f - we need to create all resources (e.g. secrets not included in KEB charts with proper annotations) needed to deploy KEB successfully. It's doable but we create environment more and more different than DEV landscape. Then we need to provide postgres to let the KEB create DB connection (unless we approach differently with some parameter letting KEB know, that no connection is supposed to be created, we just check configuration completeness).

Ad 2. We concluded with Maper that we can create additional subdirectory of resources (next to keb and cn) containing values.yaml with minimal set of settings to override our regular keb/values.yaml. Then we can use helm install keb ../keb --namespace kcp-system -f values.yaml from this directory to create kind of minimal KEB deployment.

[MarekMichali]

We decided to switch to image-builder This will allow us to create images on demand without being tied to tag creation. This will allow us to create a cleaner testing workflow with the helm install.

[PK85]

blocked waiting for Marek back from vacation