ContainerPorts SSA key is insufficiently unique - SSA fails with "duplicate" error when the contents are valid

What's the problem?

https://github.com/kubernetes/kubernetes/pull/113245#discussion_r1009911070 Validation allows: ``` ports: - containerPort: 93 hostPort: 9376 - containerPort: 93 hostPort: 7693 ``` but server-side apply does not. As of 1.29 we can SSA unrelated fields in an object with "dup ports" and even do SSA "repairs" to those fields. What we can't do is SSA them with this state in the apply. Important: this is allowed (more by accident than design) and semantically unambiguous. The defined SSA key is not sufficiently unique (`ontainerPort + protocol` -- needs to include `hostPort`). To evolve the key is tricky, but the only real alternative is atomic, which has it's own issues. Is it worth trying to find a safe way to expand an SSA key?

Why does this happen?

Automatically extracted from Kubernetes issue report. Analysis pending LLM integration.

How to fix it

Refer to the original GitHub issue for discussion and potential fixes.

#k8s#sig-network#github-issue