Fix - GCE L7 LB not picking up a custom readinessProbe URL

[guidoiaquinti]

Description

This is a fix for a GCP specific issue. The GCE L7 LB is not picking up the custom readinessProbe configurations if a port is not specified in the deployment configuration.

For more info see:

• https://stackoverflow.com/questions/44584270/how-to-get-a-custom-healthcheck-path-in-a-gce-l7-balancer-serving-a-kubernetes-i
• https://groups.google.com/g/kubernetes-users/c/lhVfyfCwEyo/m/b187gC84CwAJ
• https://github.com/kubernetes/ingress-gce/blob/master/docs/faq/gce.md#can-i-configure-gce-health-checks-through-the-ingress
• Failing to pick up health check from readiness probe kubernetes/ingress-gce#241 (comment)

In this PR we modify the deployment configuration to specify the port and we also re-enable k6 ingestion testing for the GCP e2e test (previously disabled due to this issue)

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

How has this been tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

[hazzadous]

I going to close this to reduce the noise in this repo, if it's really important feel free to open again.