feat(ci): add automatic e2e tests

[nevermarine]

Signed-off-by: Maksim Fedotov [email protected]

Description

Run automatic e2e tests on pull requests via labels.

Why do we need it, and what problem does it solve?

We need this to continuously integrate new code into an existing code base in a controlled fashion. By automating e2e tests and requiring them to pass before merging, we improve reliability of virtualization platform.

What is the expected result?

• Labeling PR with e2e/user/XXX chooses cluster where e2e tests will run
• Labeling PR with e2e/run starts e2e
• If PR doesn't have e2e/user/XXX label, e2e tests are ran on the cluster belonging to the PR author
• Labeling PR with skip/e2e removes e2e tests check

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: ci
type: feature
summary: add automatic e2e tests