Remove the logic for setting the nested protocol
field in k8s objects containing an array of ports
.
#416
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The logic was added in March 2021 as a workaround for a known k8s issue, which causes getting the declared fields for k8s objects containing an array of
ports
to fail. The fixes to the k8s issue have been merged into k8s 1.20 and 1.21:Integrate defaults marker to defaulter-gen kubernetes/kubernetes#96317 (merged in 1.20)
Fix SSA for APIService kubernetes/kubernetes#98576 (merged in 1.21).
k8s 1.21 is no longer supported on GKE and Anthos:
GKE release schedule: https://cloud.google.com/kubernetes-engine/docs/release-schedule
Anthos version and upgrade support: https://cloud.google.com/anthos/docs/version-and-upgrade-support
Therefore, we can remove the logic and related unit tests. We can keep the e2e test to make sure this change does not break things.