Add ability to provide a preconfigured KubernetesClient

[codepitbull]

Why ?

We are using the Testcontainers K3s-module (https://www.testcontainers.org/modules/k3s/) for integration tests while working on our operators.
These k8s-instances are created on the fly at test-runtime there is never a KUBECONFIG-env or something in ~/.kube/config which means that they can't be used with the default test-implementatio which uses new KubernetesClientBuilder().build()and relies on the existence of either of the two.

What ?

I added the ability to inject your own instanc eof a KubernetesClient to the builders for LocallyRunOperatorExtension and ClusterDeployedOperatorExtension.
In case none is provided it falls back to the old behaviour.

I hope this helps, feel free to leave comments for things I should change/add :)

Thanks a lot for your great work!

[scrocquesel]

+1

Aside, did you ever test https://github.com/dajudge/kindcontainer ?

[codepitbull]

+1

Aside, did you ever test https://github.com/dajudge/kindcontainer ?

Nope, but will give it a shot soon :)
Thanks for pointing out!

[csviri]

LGTM! Thank you!

just one more little thing before we merge this, could you pls run mvn clean install on the project - that will format the code - and push the changes. That will fix the failing CI job.

[codepitbull]

LGTM! Thank you!

just one more little thing before we merge this, could you pls run mvn clean install on the project - that will format the code - and push the changes. That will fix the failing CI job.

I ran it and pushed the results.

[csviri]

thank you!