Add custom object status and scale api

[juliantaylor]

The api is beta in kubernetes 1.11

Closes gh-71

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk: helpdesk@rt.linuxfoundation.org

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. I understand the commands that are listed here.

[juliantaylor]

If this file is really supposed to be written by hand like done now it should be a yaml file not json, that would avoid a huge amount of duplication via yaml anchors.

Also why are the custom object read calls named get_ while all others are called read_?

[brendandburns]

This looks good. I'm going to merge.

wrt to get* vs read* you'd have to ask @mbohlool who did the original version of this file...

wrt JSON vs YAML I don't think there is a strong feeling one way or the other. If you want to change this to YAML and the python code to load YAML instead JSON that seems fine to me.

Ultimately hand maintaining this is probably a mistake, we should generate it from the original golang struct or some-such.

Anyway, I'm going to merge this, and we can do those other things in the future.

[roycaihw]

Custom resources don't support protobuf. I'm not sure if yaml is supported though.

After a discussion with @yliaog, we want to keep the changes between beta release and GA release minimum for python-client release (I'll update devel documentation about the release procedure). We decided to not include this new API change in python-client v7.0.0. Let's fix this spec and introduce the API to v8.