support for external server

[venkataanil]

Type of change

• New feature

Description

This commit allows communication between ocp internal pod and external server. k8s-netperf client pod will use the provided ip address as the destination ip address instead of ocp server pod address. To avoid code complexity, k8s-netperf still deploys all the assets i.e server pod and service etc, however it uses the ip address provided by the user as the destination to send the traffic instead of server pod address.

User has to manually configure the external server with the required k8s-netperf driver.

To communicate with external server which has the ip 44.243.95.221, user can call k8s-netperf like below
k8s-netperf --clean=false --debug --serverIP=44.243.95.221

[capolrik]

I really like this feature! but I don't like the idea of deploying a unnecessary pod and service, it could confuse the user at then end.
You could add a bool ExternalServer to the PerfScenario struct and then check this boolean in the BuildInfra & BuildSUT functions (pkg/k8s/kubernetes.go) to avoid the unneeded deployment.

[venkataanil]

I really like this feature! but I don't like the idea of deploying a unnecessary pod and service, it could confuse the user at then end. You could add a bool ExternalServer to the PerfScenario struct and then check this boolean in the BuildInfra & BuildSUT functions (pkg/k8s/kubernetes.go) to avoid the unneeded deployment.

Thanks, thats a great suggestion. I will work on it.

[venkataanil]

As suggested, pushed a new commit which avoids deploying server pod and service. Now only client pod is deployed.

[jtaleric]

Great addition! I need to test the podPath just to make sure nothing got broken there, but used the externalServer option and it worked great! Thanks @venkataanil !!