Add kubectl port-froward to integration tests

[mabdelgowa]

Add kubectl port-froward to integration tests

[CLAassistant]

All committers have signed the CLA.

[aabouzaid]

Thanks for your contribution 🙌
I've left a couple of comments.

[aabouzaid]

Also, don't forget to rebase to get the latest updates.

[mabdelgowa]

Hi eng @aabouzaid 👋👋👋👋👋👋
I rebased my forked repo and updated the testsuite-core.yaml file with two ranges (one for port forward cmmand and another one for verification ) . recheck it right now

[aabouzaid]

@mabdelgowa, this will not work as port forwarding is a blocking command, and it will not return (will wait forever as it works).

So you can port forward and check at the same time in the script section something like this:

[...]
 range:
  - component: "Zeebe Gateway"
    serviceName: "camunda-zeebe-gateway"
    servicePort:  "26500"
    [...]
script: |
  (kubectl port-forward svc/{{ .serviceName }} {{ .servicePort }}:{{ .servicePort }} &
  curl localhost:{{ .servicePort }})

Please ensure to test it locally first to ensure the proposed change works as expected (you can test it with any service, not necessarily Camunda deployment).

[mabdelgowa]

@aabouzaid I tested it locally after editing the script line to be like this (kubectl port-forward svc/{{.value.serviceName}} {{.value.servicePort}}:{{.value.servicePort}} > /dev/null 2>&1 & curl localhost:{{.value.servicePort}}) and it passed for the opened services as it in the attached screenshots (the services which I used was camunda-zeebe-gateway --> 8080 not 26500 & camunda-operate --> 8081 ) it was only for testing

[aabouzaid]

We are now in the right direction. 👏
I've left a couple of notes.

[mabdelgowa]

@aabouzaid
check it right now
All components were capitalized, unnecessary lines were deleted, and only one line was for the script. Also, all changes were added to all versions.