-
Notifications
You must be signed in to change notification settings - Fork 39.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix unintended change of Service.spec.ports[].nodePort during kubectl apply #24180
Conversation
GCE e2e build/test passed for commit 84e975dac93f8eb43bbeb8bcee57b548a3c06749. |
Thanks @adohe. LGTM. |
I added a release note and am re-LGTMing |
So no need to make it a pointer after all? |
GCE e2e build/test failed for commit 84e975dac93f8eb43bbeb8bcee57b548a3c06749. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
GCE e2e build/test failed for commit 84e975dac93f8eb43bbeb8bcee57b548a3c06749. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
@thockin yes, no need to make it pointer. |
@adohe Tests failed. Maybe needs rebase?
|
@@ -1780,7 +1780,7 @@ type LoadBalancerIngress struct { | |||
type ServiceSpec struct { | |||
// The list of ports that are exposed by this service. | |||
// More info: http://releases.k8s.io/HEAD/docs/user-guide/services.md#virtual-ips-and-service-proxies | |||
Ports []ServicePort `json:"ports"` | |||
Ports []ServicePort `json:"ports" patchStrategy:"merge" patchMergeKey:"port"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fully backwards compatible, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@roberthbailey It will change patch and apply behavior for this resource, though the current behavior is unusable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If someone did manage to workaround this problem and was using strategic merge patch, their patches should still work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks.
84e975d
to
fcdf216
Compare
GCE e2e build/test failed for commit fcdf2161353631121005a26f2d57d97c5aa5c127. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
This PR is in an odd state. If you want to get it in as a cherrypick for 1.2.3, please get it merged soon and poke me for the cherrypick-approved label. |
I am fixing this. |
fcdf216
to
16960d3
Compare
GCE e2e build/test passed for commit 16960d3. |
@bgrant0607 ptal. |
LGTM, thanks! |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 16960d3. |
Automatic merge from submit-queue |
@adohe: Please create a cherrypick PR for this ASAP. Thanks! |
or tell us and we can do it, if you don't have time :) On Wed, Apr 20, 2016 at 10:45 AM, Zach Loafman notifications@github.com
|
I tried quickly to create one and there's a conflict:
That's as far as Zach-bot goes. |
This PR is unlikely to make it in to 1.2.3. Please tell me immediately if I need to block 1.2.3 on it. |
@zmerlynn what can I do for this? I just go back from my holiday. And now have more time to do this. |
Please follow the procedure at https://github.com/eBay/Kubernetes/blob/master/docs/devel/cherry-picks.md to create a cherry pick against |
…upstream-release-1.2 Automated cherry pick of #24180
Commit found in the "release-1.2" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
…of-#24180-upstream-release-1.2 Automated cherry pick of kubernetes#24180
…of-#24180-upstream-release-1.2 Automated cherry pick of kubernetes#24180
UPSTREAM: 82705: use controller to publish cluster authentication info Origin-commit: bd8621462110dc03396cc304b3579281e184840a
UPSTREAM: 82705: use controller to publish cluster authentication info Origin-commit: bd8621462110dc03396cc304b3579281e184840a
Please refer #23551 for more detail. @bgrant0607 I think this simple fix should be ok to reuse nodePort. @thockin ptal.
Release note: Fix unintended change of
Service.spec.ports[].nodePort
duringkubectl apply
.