This repository was archived by the owner on Apr 25, 2023. It is now read-only.
retain healthCheckNodePort for service when updating #1347
Merged
+97
−0
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.
Signed-off-by: Bruce Ma brucema19901024@gmail.com
What this PR does / why we need it:
For services which type==LoadBalancer and externalTrafficPolicy==Local, their field
spec.healthCheckNodePort
will be allocated by APIServer, and after that it should be unchangeable, so we should retain this field during update, just likespec.clusterIP
andnodePort
in ports.Here we don't need to check whether the desired service need
healthCheckNodePort
but just pass it on, because if the passedhealthCheckNodePort
is not needed any more, it will be recycled by APIServer.Special notes for your reviewer:
Codes in kubernetes about the validation on
spec.healthCheckNodePort
, https://github.com/kubernetes/kubernetes/blob/68108c70e29a74bb455ab63adeb5725a37e94e4f/pkg/registry/core/service/storage/rest.go#L369