Why does deleteNamespacedServiceAccount return V1ServiceAccount while other resources delete methods return V1Status?

[liavyona]

I have a list of resources which I work generic with (using reflection). I have a list of future tasks to delete them all. All resources delete methods return V1Status while deleteNamespacedServiceAccount returns V1ServiceAccount why is that?

[liavyona]

I tried to convert it myself by:

        if ("ServiceAccount".equals(kind)) {
            Call call = ((CoreV1Api) api).deleteNamespacedServiceAccountCall(name, namespace, null, null, null, null, null, null, null);
            Type returnType = (new TypeToken<V1Status>() {
            }).getType();
            ApiResponse<V1Status> response = ((CoreV1Api) api).getApiClient().execute(call, returnType);
            return (V1Status) response.getData();
        }

It returns successfully but the details and status attributes are null.

[liavyona]

I found that this commit changed the return type of deleteNamespacedServiceAccount alongside other kubernetes resources which have been changed too (PersistVolume, Pod etc.). On the other hand, Service, Secret, ConfigMap and others remain the same. Why is that? What benefit do I have from getting the object I just deleted? V1Status can tell me whether the deletion completed successfully.
@brendandburns Why there is no aligned API to whole resources?

[brendandburns]

All of this is generated from the Kubernetes OpenAPI specification here:

https://raw.githubusercontent.com/kubernetes/kubernetes/master/api/openapi-spec/swagger.json

The truth is that delete can either return a V1Status or the object itself (see #86 for more discussion) but this isn't well represented in the OpenAPI specification.

If we wanted to correct this, we need to update the OpenAPI specification. (and also update the client generator to handle multi-return), that's not a bad thing to do, but it's also not a super high priority.

Hope that helps.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.