Allow E2E suite test to run against a remote cluster

[squakez]

With a limited resource machine, then, you have no other option to delegate E2E work remotely. So, I am thinking that maybe we can introduce a couple of environment variables when installing the operator in the E2E suite [1] which can control the following parameters:

      --operator-image string                       Set the operator Image used for the operator deployment
      --operator-image-pull-policy string           Set the operator ImagePullPolicy used for the operator deployment

so, the final user can override them to look for a custom image (like in your case) or controlling the pull policy. I am opening an issue to work on this separately, and feel free to contribute to it as well. In the while, if you are not able to run things locally, I suggest to push the changes and have a look at the checks result. Fortunately now the time to complete a full cycle of test is less that 1 hour.

[1]

camel-k/e2e/support/test_support.go

Line 325 in b79bb26

cmdArgs = []string{command, "-n", namespace, "--operator-id", operatorID}

Originally posted by @squakez in #4190 (comment)

[squakez]

FYI @mertdotcc

[mertdotcc]

Thank you @squakez! Can't wait to try it out!