Add e2e tests for project

[marcofranssen]

Since we bumped to the latest operator-sdk we have a failing workflow for e2e tests. This is caused because this project doesn't have proper e2e tests implemented just yet.

For the quality guarantee of this project it would be good if we add the first coverage of e2e tests.

Probably check another operator on how to implement those.

[LeonLow97]

Hi @marcofranssen , I would like to work on this but I have some questions:

• What kind of “e2e tests” (Kubernetes deployment tests? API CRD validation?).
• What “another operator” should I look at? Or I look for one myself.
• Is this the file location to add the e2e test? https://github.com/fluent/fluent-operator/tree/master/tests

[marcofranssen]

See https://github.com/fluent/fluent-operator/blob/master/Makefile#L82

Probably scaffold a new project using the operator sdk to figure out the structure and then copy over those parts to this project which was created with an earlier version of the operator-sdk and therefore lacking the e2e tests.

https://sdk.operatorframework.io/docs/building-operators/golang/testing/

[!Note] Preferably make smaller PRs slowly adding coverage for smaller chunks of functionality.

[LeonLow97]

Thanks @marcofranssen for the advices, I will look into this issue 😄