UPSTREAM: <carry>: patch in a non-standard location for apiservices

[deads2k]

OpenShift has stored apiservices in a non-standard location. This codifies that into a patch since we have no need to support the old location.

@liggitt is there an easy way for me to look at this directly?

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• vendor/k8s.io/kubernetes/cmd/kube-apiserver/OWNERS [deads2k]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[liggitt]

@liggitt is there an easy way for me to look at this directly?

not sure what you mean

[liggitt]

you mean viewing in etcd, like ETCDCTL_API=3 etcdctl get / --prefix --keys-only | grep apiservices?

[deads2k]

thanks.

ETCDCTL_API=3 etcdctl get / --prefix --keys-only --cert=openshift.local.clusterup/kube-apiserver/master.etcd-client.crt --key=openshift.local.clusterup/kube-apiserver/master.etcd-client.key --cacert=openshift.local.clusterup/kube-apiserver/etcd.server.crt --endpoints=127.0.0.1:4001 | grep apiservices

/hold

holding until I test it in cluster up

[deads2k]

/hold cancel

confirmed in my kubeapiserver branch