Fix Kubernetes test scenario

[gtroitsk]

Summary

Fix issue #433

Now services are exposed with NodePort instead of LoadBalancer
KubectlClient was updated to use the new functions from Fabric8 Kubernetes client, deprecated functions were removed.

Existing Kubernetes test coverage was run locally with connection to temporary Kubernetes cluster.

I add KubernetesPostgresqlIT to test containers creating for basic scenario.

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[gtroitsk]

run kube tests

[gtroitsk]

run kube tests

[michalvavrik]

I don't really have comments as long as it works (CI is red), because the code looks ok on the first look. I'll re-check when the CI is green, but I don't expect issues.

Just one question - what will happen if I run K8 tests from 2 different PRs at one time? Is the host always specific to the ephemeral namespace?

[gtroitsk]

run kube tests

[gtroitsk]

I don't really have comments as long as it works (CI is red), because the code looks ok on the first look. I'll re-check when the CI is green, but I don't expect issues.

Just one question - what will happen if I run K8 tests from 2 different PRs at one time? Is the host always specific to the ephemeral namespace?

Host allows to use ephemeral namespace. I don't expect problems running k8s tests in multiple PRs at one time

[michalvavrik]

Good job!