chore: migrate from kuttl to chainsaw

[eddycharly]

This PR migrates e2e tests from kuttl to chainsaw.

Chainsaw was created because kuttl stopped to be actively maintained (it's actually a single maintainer now).

We are also solving most of the kuttl limitations that exist today and wrote a command to automatically migrate from kuttl to chainsaw. It supercharges e2e tests with better logs, config maps assertions, assertions trees and many more things 💪

This is a relatively young project but it has already been adopted by a couple of e2e tests heavy projects (kyverno, keptn, fairwinds rbac-manager, grafana-operator, redis-operator and others).

To give more context, you can see similar PRs at:

• chore: replace kuttl tests with chainsaw keptn/lifecycle-toolkit#3000
• feat: add chainsaw scorecard test support operator-framework/operator-sdk#6676
• chore: migrate from kuttl to chainsaw grafana/tempo-operator#786 in this PR the tempo-operator maintainers asked some good questions and I explained the current status, that I suggest taking a look at.

Sadly, kuttl haven't done a release since jan 2023.

Here you can find a good video showcasing chainsaw: https://www.youtube.com/watch?v=Ejof-wtAdQM&ab_channel=CamilaMacedo

To make things more concrete, there are a couple of issues in this repo, a few files are not valid and kuttl doesn't complain because unmarshalling is not strict so the non-valid fields are simply ignored. This is a problem because the behaviour of the tests is not the expected one, for example:

• opentelemetry-operator/tests/e2e-opampbridge/opampbridge/00-assert.yaml

  Lines 67 to 70 in c534eaf

  	apiVersion: kuttl.dev/v1beta1
  	kind: TestAssert
  	opampbridges:
  	- selector: app.kubernetes.io/component=opentelemetry-opamp-bridge

• opentelemetry-operator/tests/e2e-prometheuscr/create-sm-prometheus-exporters/07-delete.yaml

  Lines 6 to 8 in 94c8420

  	metadata:
  	name: simplest
  	namespace: create-sm-prometheus

If you need more infos 👇

• GitHub: https://github.com/kyverno/chainsaw
• Docs: https://kyverno.github.io/chainsaw
• Slack: https://kubernetes.slack.com/archives/C067LUFL43U

[iblancasa]

cc/ @IshwarKanse

[swiatekm]

Some comments on managing chainsaw in a local environment.

[eddycharly]

Quick blog post covering chainsaw two major new features in v0.1.4 https://kyverno.io/blog/2024/02/15/kyverno-chainsaw-0.1.4-awesome-new-features/ 🤩

[IshwarKanse]

@eddycharly The work done on Chainsaw is really impressive. I'm looking forward to use it for other operator testing as well and for our internal QE testing.

[eddycharly]

@eddycharly The work done on Chainsaw is really impressive. I'm looking forward to use it for other operator testing as well and for our internal QE testing.

@IshwarKanse glad to know you like it !

[eddycharly]

Not sure what breaks here, probably something simple but i fail to spot it 🙈

[eddycharly]

Hope i fixed it now 🤞