Typo

Revert jenkins/e2e.sh back to 606b517a, minus -tap

Check Docker version in Kubelet /healthz handler

Add more logging

Fix jenkins/hack/e2e.sh, log errors better

Pervert e2e shell tests to run under Ginkgo

To fix this, it would be an alias for:

  hack/ginkgo-e2e.sh -t TestNetwork

... which may not work on binary distributions, because it's relying
on test assets, so it probably shouldn't live in cluster/ ...

* Add a test/e2e/shell.go that slurps up everything in hack/e2e-suite
and runs it as a bash test, borrowing all the code from hack/e2e.go.

* Rip out all the crap in hack/e2e.go that deal with multiple tests

* Move hack/e2e-suite/goe2e.sh to hack/ginkgo-e2e.sh so that it
doesn't get slurped up.

contrib: add git-sync container

Clarify commenting in endpoints_controller

Make the replication controller more resilient to event expiration in watch.

kubectl proxy: make static prefix configurable

Fix tests in validation_test

Deleting the API objects related to /operations

Remove kubecfg from all getting started docs.

Make e2e shell tests work standalone

Simply incorporate some of the boilerplate from hack/e2e.go into the
scripts in hack/e2e-suite.

Use environment variables with default values to allow overrides in
kubectl command line and to use a versioned package root.

Tested:
- Ran `go run hack/e2e.go -test` on a test cluster.
- Ran the test cases individually.
- Ran hack/e2e-suite/goe2e.sh -t Pods to confirm it takes arguments.
- Also fixed cluster/test-network.sh (which should be more and more irrelevant.)

Adding swagger files which got left out of last PR

Wait until containers actually finish running before trying to clean up

volumes or pods.

Use a custom namespace for running liveness e2e test cases.

Report the found minions during validation of cluster

This will allow us greated isolation between test case runs without the
need to include randomized uuids to many of the fields in the pods,
services and rcs creation requests.

Tested:
- Ran two instances of `e2e -t TestLivenessHttp -t TestLivenessExec`
  simultaneously and confirmed that pod names did not clash and that
  both of them completed successfully.

Use replication controller for redis master.

Updating swagger-ui code to the latest version and removing the 'Try it out' buttons

Some tests expect the error cases to fail for a specific reason, but they could
fail for other reasons and still pass. This caused some changes to break the
tests without noticing the breakage. Example are the recent defaulting PR

This change fixes such tests and also updates some obsolete tests.

Add user agent string to all client requests