Add support for Server Side Apply

[xaviersierra]

Server Side Apply

Starting from kubernetes 1.16, Server Side Apply it's enabled by default.

This feature is very useful from a operator development point of view,
since it would require fewer requests to the Kubernetes API during the reconciliation cycle.

Using Server Side Apply has also the advantage that inform to users
who owns which field of a given resource.

Proposed Change

Add a boolean field to the io.fabric8.kubernetes.client.dsl.base.PatchContext named serverSide. That if it's true, sets the request content type to application/apply-patch+yaml.

[rohanKanojia]

Related to #2454

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[shawkins]

Fabric8 6 will support server side apply with a patch call:

client.services().withName("name").patch(PatchContext.of(PatchType.SERVER_SIDE_APPLY), service);

you may need to force it if the resource was not created using the fabric8 server side apply:

client.services().withName("name").patch(new PatchContext.Builder().withPatchType(PatchType.SERVER_SIDE_APPLY).withForce(true).build(), service);

[tacf]

@shawkins Doesn't this solution provide a way to patch through the use of manifests? As in, does this only allow patching with the use of code defined objects?

[shawkins]

As in, does this only allow patching with the use of code defined objects?

There are other patch methods that accept the patch as a string if you don't want to use the object representation.