k3s/pkg/registry/core
Kubernetes Submit Queue 212234ab3f Merge pull request #39807 from deads2k/client-02-client-go
Automatic merge from submit-queue

run staging client-go update

Chasing to see what real problems we have in staging-client-go.

@sttts you get similar results?
2017-01-13 13:21:19 -08:00
..
componentstatus start the apimachinery repo 2017-01-11 09:09:48 -05:00
configmap mechanical repercussions 2017-01-13 08:27:14 -05:00
controller mechanical repercussions 2017-01-13 08:27:14 -05:00
endpoint mechanical repercussions 2017-01-13 08:27:14 -05:00
event mechanical repercussions 2017-01-13 08:27:14 -05:00
limitrange mechanical repercussions 2017-01-13 08:27:14 -05:00
namespace mechanical repercussions 2017-01-13 08:27:14 -05:00
node mechanical repercussions 2017-01-13 08:27:14 -05:00
persistentvolume mechanical repercussions 2017-01-13 08:27:14 -05:00
persistentvolumeclaim mechanical repercussions 2017-01-13 08:27:14 -05:00
pod Merge pull request #39814 from deads2k/api-58-multi-register 2017-01-13 12:37:02 -08:00
podtemplate mechanical repercussions 2017-01-13 08:27:14 -05:00
rangeallocation Enable auto-generating sources rules 2017-01-05 14:14:13 -08:00
resourcequota mechanical repercussions 2017-01-13 08:27:14 -05:00
rest mechanical repercussions 2017-01-13 08:27:14 -05:00
secret mechanical repercussions 2017-01-13 08:27:14 -05:00
service use apimachinery packages instead of client-go packages 2017-01-13 14:04:54 -05:00
serviceaccount mechanical repercussions 2017-01-13 08:27:14 -05:00
OWNERS Update OWNERS approvers and reviewers: pkg/registry 2016-12-19 16:22:40 -08:00