Fix Content-Type header for status subresource PATCH requests

[Copilot]

GenericKubernetesApi.updateStatus() was sending PATCH requests with application/json Content-Type, causing 415 errors. The Kubernetes API requires application/json-patch+json for JSON Patch operations.

Changes

• GenericKubernetesApi.makeUpdateStatusCallBuilder(): Wrap status patch calls with adaptPatchCall() to set V1Patch.PATCH_FORMAT_JSON_PATCH content type, matching the behavior of existing patch() methods

• Test update: Add Content-Type header verification to updateStatusNamespacedJobReturningObject()

Example

var fooApi = new GenericKubernetesApi<>(Foo.class, FooList.class, "foo.bar", "v1", "foos", apiClient);
// Now correctly sends Content-Type: application/json-patch+json
fooApi.updateStatus(foo, Foo::getStatus).throwsApiException().getObject();

Previously failed with:

the body of the request was in an unknown format - accepted media types include: 
application/json-patch+json, application/merge-patch+json, application/apply-patch+yaml

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Content type for PATCH sub resource requests is incorrect</issue_title>
<issue_description>Describe the bug
Patching status subresource of a CRD always fails with java client.

Client Version
20.0.0

Kubernetes Version
1.29.1

Java Version
Java 17

To Reproduce

var fooApi = new GenericKubernetesApi<>(Foo.class, FooList.class, "foo.bar", "v1", "foos", apiClient);
fooApi.updateStatus(foo, Foo::getStatus).throwsApiException().getObject();

Above code always fails with the following error

{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the body of the request was in an unknown format - accepted media types include: application/json-patch+json, application/merge-patch+json, application/apply-patch+yaml","reason":"UnsupportedMediaType","code":415}

Expected behavior
This call is expected to succeed.

KubeConfig
If applicable, add a KubeConfig file with secrets redacted.

Server (please complete the following information):

• OS: MacOS
• Kind cluster

Additional context
The equivalent call from kubectl succeeds -

kubectl patch foos.foo.bar foo1 --subresource=status --type=json -p '[{"op":"replace","path":"/status","value":{"availableReplicas":20}}]'

In kubernetes/api/openapi.yaml, operationId: patchNamespacedCustomObject has the content type defined as application/json, which seem to be incorrect.
</issue_description>

<agent_instructions>Please create a PR to make GenericKubernetesApi.updateStatus() and patch() use the PatchUtils internally.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@brendandburns Yeah, there's lots of errors in the upstream YAML. We try to fix them when we find them. @brendandburns Also, see the patch example here:

https://github.com/kubernetes-client/java/blob/master/examples/examples-release-latest/src/main/java/io/kubernetes/client/examples/PatchExample.java</comment_new>

• Fixes Content type for PATCH sub resource requests is incorrect #3143

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[yue9944882]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Copilot, yue9944882

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [yue9944882]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment