Kubernetes Submit Queue 4a223efd27 Merge pull request #34573 from errordeveloper/fix-early-deployment-issue ...

Automatic merge from submit-queue

Test API more extensivelly before declaring readiness 

**What this PR does / why we need it**:

It's possible that first deployment kubeadm creates will hit `deployments.extensions "kube-discovery" is forbidden: not yet ready to handle request`, which comes from NamespaceLifecycle admission controller and has something to do with cache. According to @derekwaynecarr, we need to create a namespace-scoped resource to really check for this. I didn't want to make a check with deployment of whatever comes first right now, and decided to have explicit step for this in `apiclient.go`.

**Which issue this PR fixes**: fixes #34411

**Special notes for your reviewer**: @kubernetes/sig-cluster-lifecycle 

**Release note**:
```release-note
NONE
```

2016-10-13 01:44:24 -07:00

..

app

Merge pull request #34573 from errordeveloper/fix-early-deployment-issue

2016-10-13 01:44:24 -07:00

kubeadm.go

Cleanup some low-hanging fruits and review TODOs

2016-09-24 14:46:40 +01:00

OWNERS

kubeadm: add OWNERS file

2016-09-28 13:52:27 -07:00