Fix: service targetPort error when ExternalName service targetPort not a number

[wangfeiing]

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

service ports targetPort is a string that not a number，nginx will get endpoints that port is 0
for example

apiVersion: v1
kind: Service
metadata:
  labels:
    app: foo
  name: foo-svc
  namespace: test
spec:
  externalName: www.google.com
  ports:
  - name: http
    port: 8080
    protocol: TCP
    targetPort: http
  selector:
    foo: kms-server
  sessionAffinity: None
  type: ExternalName

nginx get endports port field is 0

{
    "endpoints": [
        {
            "address": "www.google.com",
            "port": "0"
        }
    ],
    "service": {
        "metadata": {
            "creationTimestamp": null
        },
        "spec": {
            "sessionAffinity": "None",
            "selector": {
                "app": "foo"
            },
            "type": "ExternalName",
            "ports": [
                {
                    "targetPort": "http",
                    "protocol": "TCP",
                    "name": "http",
                    "port": 8080
                }
            ],
            "externalName": "www.google.com"
        },
        "status": {
            "loadBalancer": {}
        }
    },
    "noServer": false,
    "sslPassthrough": false,
    "trafficShapingPolicy": {
        "weight": 0,
        "header": "",
        "headerValue": "",
        "headerPattern": "",
        "cookie": ""
    },
    "sessionAffinityConfig": {
        "cookieSessionAffinity": {
            "name": ""
        },
        "name": "",
        "mode": ""
    },
    "name": "test-foo-svc-8080",
    "upstreamHashByConfig": {
        "upstream-hash-by-subset-size": 3
    },
    "port": 8080
}

How Has This Been Tested?

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added unit and/or e2e tests to cover my changes.
• All new and existing tests passed.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: wangfeiing / name: 北巷 (5971fbe)

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx canceled.

Name	Link
🔨 Latest commit	5971fbe
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/658e82b1e1401900089d1dd3

[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.

Details

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]

Welcome @wangfeiing!

It looks like this is your first PR to kubernetes/ingress-nginx 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/ingress-nginx has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @wangfeiing. 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.

Details

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: wangfeiing
Once this PR has been reviewed and has the lgtm label, please assign rikatz for approval. For more information see the Kubernetes Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[wangfeiing]

All tests have passed. So i think we can merge this pr :)

[k8s-ci-robot]

@wangfeiing: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/retest

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.

[wangfeiing]

/retest

[k8s-ci-robot]

@wangfeiing: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/retest

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.

[github-actions]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

[k8s-triage-robot]

The lifecycle/frozen label can not be applied to PRs.

This bot removes lifecycle/frozen from PRs because:

• Commenting /lifecycle frozen on a PR has not worked since March 2021
• PRs that remain open for >150 days are unlikely to be easily rebased

You can:

• Rebase this PR and attempt to get it merged
• Close this PR with /close

Please send feedback to sig-contributor-experience at kubernetes/community.

/remove-lifecycle frozen