Multiple protocols are clobbered when rendering ports

[cmhillerman]

In the ports section of a manifest, if you are trying to set UDP and TCP for a port, only one of the ports is rendered in kustomize. E.g. If you have:

        ports:
            - containerPort: 53
              hostPort: 53
              hostIP: 0.0.0.0
            - containerPort: 53
              hostPort: 53
              protocol: UDP
              hostIP: 0.0.0.0

And when you run kustomize build you get:

        ports:
        - containerPort: 53
          hostIP: 0.0.0.0
          hostPort: 53

This is because containerPort is used as the key to the hash. Maybe if we forced people to use name in all ports and used that as the key? Or using name as the key if the name exists?

I also could be confused and there's a workaround or something I'm missing?

[mengqiy]

@monopole @Liujingfang1 Please check kubernetes/kubernetes#39188 for the root cause.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.