Nikhita Raghunath c4f02185e3 core/v1 should be first in discovery order ...

Currently, core/v1 is in the end of the discovery order.

Since core/v1 is special, it should be in the beginning.

Kubernetes-commit: 45950fdb750d7ac12cec3b9ef3487baa99a40401

2018-02-05 15:04:29 +05:30

..

cached

Autogenerate BUILD files

2017-12-23 13:06:26 -08:00

fake

[client-go] fake discovery returns server groups

2017-10-11 14:21:29 -04:00

BUILD

update BUILD files

2017-10-12 13:52:10 -07:00

discovery_client_test.go

core/v1 should be first in discovery order

2018-02-05 15:04:29 +05:30

discovery_client.go

core/v1 should be first in discovery order

2018-02-05 15:04:29 +05:30

helper_blackbox_test.go

remove duplicated import

2017-11-14 11:36:32 +08:00

helper.go

stop setting bad defaults that are indistinguishable from real values for clients

2017-05-17 17:20:30 +00:00

restmapper_test.go

kubectl: Remove swagger 1.2 entirely.

2017-09-28 15:58:53 -07:00

restmapper.go

use specified discovery information if possible

2017-09-22 11:22:07 +00:00

unstructured.go

Scheme should provide ObjectTyper for Unstructured objects as well

2017-11-14 22:25:24 -05:00