Enable update staging client in master.

[k82cn]

Enable update staging client in master.

[k8s-reviewable]

This change is 

[eparis]

/approve

[eparis]

/lgtm

[k8s-github-robot]

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

[deads2k]

Removing this from the merge queue until #39099 is settled.

[deads2k]

@caesarxuchao This enables auto-updating. I think this should wait until we sort out how to handle client-go vendoring. I think it should be done as part of a sync to client-go.

[deads2k]

I think we need to split the copy script into a script that copies the API types from k8s.io/kubernetes and a script that generates the client directly into client-go. After that, we do NOT run the vendoring step in kubernetes. Instead, there should be a client-go sync script like we have for apimachinery. If a bot were to sync all repos against the same kubernetes, the vendor dir could be built during that step and it would always have a matching set and we have no cycles.

[caesarxuchao]

The process you proposed will work if there are only api/ and apis/ under client-go/pkg/. Otherwise staging/client-go will not compile because these other packages under staging/client-go/pkg/ can be out of date.

I will write an alternative approach in kubernetes/client-go#78, let's see if it's more intuitive.

[k8s-github-robot]

/lgtm cancel //PR changed after LGTM, removing LGTM. @deads2k @eparis @k82cn

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

The following people have approved this PR: k82cn

Needs approval from an approver in each of these OWNERS Files:

• hack/OWNERS

We suggest the following people:
cc @ixdy
You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[k82cn]

@caesarxuchao / @deads2k , thanks for your comments :). how about juts delete those lines comments?

[k8s-ci-robot]

@k82cn: The following test(s) failed:

Test name	Commit	Details	Rerun command
Jenkins GCE etcd3 e2e	7789cf3	link	@k8s-bot gce etcd3 e2e test this

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[deads2k]

The process you proposed will work if there are only api/ and apis/ under client-go/pkg/. Otherwise staging/client-go will not compile because these other packages under staging/client-go/pkg/ can be out of date.

Using go list you'd be able to pick up the dependencies (and transitives) too.

[caesarxuchao]

godep save under the hood is the same as go list.

I'm not too excited about generating clients in the publishing robot, it makes client-go's publishing process different from other repos. I think this idea is easier to think about. (oh I see you commented that idea is good, I'll experiment it and push something tomorrow)

[caesarxuchao]

I think mainly I need to update the publishing robot to checkout the latest apimachinary and vendor it before publishing to k8s.io/client-go. I'll code it up tmr. I'll clean up copy.sh as well, but maybe we are not on the same page about copy.sh, we'll see :)