Add e2e test in build workflows

[JorTurFer]

Signed-off-by: Jorge Turrado jorge_turrado@hotmail.es

As a first step to support ARM64, this PR adds another job after building the images that does a e2e test.
This extra job basically does these actions:

1. Install KEDA using helm
2. Install the http-add-on using helm with canary/VERSION tag
3. Install the sample using helm
4. Check that the SO generated based on the HTTPScaledObject is ready (.status.Ready == True)
5. Check that the workload has 0 instances
6. Do a request
7. Check that the workload has 1 instance

Note: Latest chart doesn't work with canary tag because right now, canary need an extra configuration that is not merged and released with the chart yet. You can check how it works here

Checklist

• Commits are signed with Developer Certificate of Origin (DCO)
• Any necessary documentation is added, such as:
  • README.md
  • The docs/ directory
  • The docs repo

Related #364

[arschles]

@JorTurFer looks great! can you pull the scripts into separate files under a top-level tests/ directory or something like that?

[JorTurFer]

Hey!
Sure, tomorrow I'll do it :)

[JorTurFer]

Hi @arschles ,
I have changed a bit the script to cover also a simple e2e test and not only the smoke test.
You can see it working in this CI and failing (I have provocated a failure not scaling to the target value) in this CI
This PR still requires the new version of the chart with the needed value for working with canary (just to not merge this till the next chart version is released)

[arschles]

@JorTurFer this looks good to me, thanks 👍

[JorTurFer]

The test is failing due to this feature is needed in the chart (I wrote it in the PR description xD)
Can we release new chart version?

[v-shenoy]

@JorTurFer I was working on adding e2e and stress tests as a part of this - #238 (Go-based, similar to keda core). But I see that you've added one here. What should I do then @JorTurFer ?

[JorTurFer]

@JorTurFer I was working on adding e2e and stress tests as a part of this - #238 (Go-based, similar to keda core). But I see that you've added one here. What should I do then @JorTurFer ?

If you are introducing e2e using go, go ahead 🙂. I did this several months ago as a pre step for supporting arm builds. My intention was having at least one "happy path", that's why I used bash but obviously, using golang is better :)

[JorTurFer]

In fact, current approach has strong dependency with the helm chart because I used it to simplify the deploy process and that's not the best IMO