Tim Hockin cb95c479cb Fix polarity of a test in NodePort allocation ...

The result of this was that an update to a Service would release the
NodePort temporarily (the repair loop would fix it in a minute).  During
that window, another Service could get allocated that Port.

2017-03-16 17:19:26 -07:00

..

componentstatus

added short names for resources which are exposed during discovery

2017-02-06 23:35:07 +01:00

configmap

Updating the registry to return whether the resource was immediately deleted

2017-02-21 11:00:35 -08:00

endpoint

Updating the registry to return whether the resource was immediately deleted

2017-02-21 11:00:35 -08:00

event

added short names for resources which are exposed during discovery

2017-02-06 23:35:07 +01:00

limitrange

added short names for resources which are exposed during discovery

2017-02-06 23:35:07 +01:00

namespace

API

2017-02-28 23:05:40 -08:00

node

Updating the registry to return whether the resource was immediately deleted

2017-02-21 11:00:35 -08:00

persistentvolume

Validation PVs for mount options

2017-03-09 18:24:37 -05:00

persistentvolumeclaim

added short names for resources which are exposed during discovery

2017-02-06 23:35:07 +01:00

pod

fix go vet issues

2017-02-27 21:24:45 -08:00

podtemplate

Update generated files

2017-02-03 08:15:46 +01:00

rangeallocation

…

replicationcontroller

Updating the registry to return whether the resource was immediately deleted

2017-02-21 11:00:35 -08:00

resourcequota

added short names for resources which are exposed during discovery

2017-02-06 23:35:07 +01:00

rest

Update bazel

2017-02-15 10:25:15 +01:00

secret

Updating the registry to return whether the resource was immediately deleted

2017-02-21 11:00:35 -08:00

service

Fix polarity of a test in NodePort allocation

2017-03-16 17:19:26 -07:00

serviceaccount

Updating the registry to return whether the resource was immediately deleted

2017-02-21 11:00:35 -08:00

OWNERS

…