Both Custom Resource Definitions and Custom Resources strip the spec from their object.

As you can see here:

        "spec": {
            "conversion": {
                "strategy": "None"
            },
            "group": "stable.example.com",
            "names": {
                "kind": "CronTab",
                "listKind": "CronTabList",
                "plural": "crontabs",
                "shortNames": [
                    "ct"
                ],
                "singular": "crontab"
            },
            "scope": "Namespaced",
            "versions": [
                {
                    "name": "v1",
                    "schema": {
                        "openAPIV3Schema": {
                            "type": "object"
                        }
                    },
                    "served": true,
                    "storage": true
                }
            ]
        },

The openAPIV3Schema object is truncated.

This happens on write and on read. The above output truncated the response after the full object was written via a different client and was verified to not truncate it when reading from those clients.

Likewise, when the openAPIV3Schema object is entact, Custom Resource writes fail to send the spec for that CR. This happens after successfull CR writes with other clients.

kubernetes-client / c

Both Custom Resource Definitions and Custom Resources strip the spec from their object. #223