-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
Support strategic merge patch for custom resources #58414
Comments
/area custom-resources |
I'm not sure I agree. Strategic merge patch has proved problematic both client-side and server-side. Designing a major addition to it seems like an investment in a direction we don't want to go. |
Let's clarify: we need PATCH conflict retries for CRDs. If that is through SMP or something else does not matter. Or we officially accept that the PATCH behaviour is different for CRDs. Not sure we want this kind compromises. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
I'm not sure if we are going to support this but removing the stale label until it is decided what to do. /remove-lifecycle stale |
Didn't see this until now.
I currently don't want to expand support for SMP. I do want to permit 3 way
merge via apply.
JSONPatch and JSON merge patch should work today, I think?
…On Fri, Apr 20, 2018 at 2:36 AM Nikhita Raghunath ***@***.***> wrote:
I'm not sure if we are going to support this but removing the stale label
until it is decided what to do.
/remove-lifecycle stale
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#58414 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAnglhSAcsEwTUk-vnVSS7caM3QFxuXcks5tqawxgaJpZM4Rh-xS>
.
|
Yes, they do. 👍 |
https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#advanced-features-and-flexibility says for strategic-merge-patch / CRDs column: "No, but similar functionality planned". Should this be updated to "No" or "Not planned"? |
@cben Thanks for pointing it out. Created kubernetes/website#10994 to say "No". |
We should support strategic merge patch (smp) for custom resources if we plan to move CRDs to GA [1].
Currently, we face the following issues with regards to not supporting strategic merge patch:
/cc @sttts @deads2k @enisoc @mbohlool @liggitt @lavalamp @caesarxuchao @jennybuckley
[1] https://groups.google.com/forum/#!topic/kubernetes-sig-api-machinery/07JKqCzQKsc
The text was updated successfully, but these errors were encountered: