Remove curl dependencies in e2e tests #9716

[sonbui00]

What this PR does / why we need it:

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

fixes #9716

How Has This Been Tested?

ginkgo  --trace --focus "should return 200 when service has topology hints" ./e2e.test
ginkgo  --trace --focus "should update the external name after a service update" ./e2e.test
ginkgo  --trace --focus "should use the Service Cluster IP and Port" ./e2e.test
ginkgo  --trace --focus "should not use the Service Cluster IP and Port" ./e2e.test
ginkgo  --trace --focus "overriding what's set from the upstream" ./e2e.test

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

Hi @sonbui00. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx ready!

Name	Link
🔨 Latest commit	57aaceb
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/64d6214597c6d600078a6a19
😎 Deploy Preview	https://deploy-preview-10296--kubernetes-ingress-nginx.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[rikatz]

/ok-to-test
This is great! Thanks!

/cc @strongjz for the second pass

[k8s-ci-robot]

@rikatz: GitHub didn't allow me to request PR reviews from the following users: the, second, pass, for.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/ok-to-test
This is great! Thanks!

/cc @strongjz for the second pass

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rikatz]

@sonbui00 with this passing you can probably remove curl from e2e test image build?

[sonbui00]

@sonbui00 with this passing you can probably remove curl from e2e test image build?

@rikatz sure. just wait review and merge this first

[tao12345666333]

thanks

[strongjz]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sonbui00, strongjz, tao12345666333

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [strongjz,tao12345666333]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment