CI pipeline for backend switching tests

[mfaizanse]

Setup CI

Setup the CI job to execute the e2e test from #74.

Job Steps:

• Install gardener cluster
• Install nats-module (latest release) and wait for readiness.
• Deploy eventing-manager (from PR).
• Create Eventing CR with NATS
• Run end-to-end tests (make e2e-eventing-setup and make e2e-eventing)
• Update Eventing CR to EventMesh
• Run end-to-end tests (make e2e-eventing)
• Update Eventing CR back to NATS
• Run end-to-end tests (make e2e-eventing and make e2e-cleanup)

Acceptance

• Execute the e2e script using github action.
• Run it on PRs and main.

Implementation hints

• store secrets for EM, IAS and Gardener securely so that they can be used by the github action

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

[kyma-bot]

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

[kyma-bot]

@kyma-bot: Closing this issue.

In response to this:

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[grischperl]

/remove-lifecycle stale

[mfaizanse]

#388
#392
#391