models do not set kind or apiversion

[juliantaylor]

The models do not set the kind and apiVersion when created:

In [12]: k8s.client.models.v1_service.V1Service()
Out[12]: 
{'api_version': None,
 'kind': None,
 'metadata': None,
 'spec': None,
 'status': None}

Both the kind and api version are known to the model so they should set it.

[splattner]

I see the same behaviour.

[micw523]

I would question if we could fix these. The constructors for such model objects are fairly dumb and are generated by a generator.

[splattner]

I think the PodList in the Response from the API Server does not include the kind & apiVersion fields in the items

GET https://kubernetes/api/v1/pods

{
    "kind": "PodList",
    "apiVersion": "v1",
    "metadata": {
        "selfLink": "/api/v1/pods",
        "resourceVersion": "127396924"
    },
    "items": [
        {
            "metadata": {   ...   },
            "spec": {   ...   },
            "status": {   ...   },
         }
   ]
  (...)
}

and therefore kind & apiVersion are none
So this is not a Problem with the Python Client.

But now the question, why is kind and apiVersion not included in the Response?

[juliantaylor]

This issue is about the models in the client and may indeed be a bit tricky to fix.
The consequences for api calls is issue #745

[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-testing, kubernetes/test-infra and/or fejta.
/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-testing, kubernetes/test-infra and/or fejta.
/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-testing, kubernetes/test-infra and/or fejta.
/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-testing, kubernetes/test-infra and/or fejta.
/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.