This was missing, and wasn't versioned. It now is.

This test creates a gameserver and connect to it

update vendor with required lib for e2e
Adds the gcloud builder step to test it in a special e2e cluster
Updates build documentations with e2e instructions
Adds minikube e2e target

Keeping up with Kubernetes versions, as well as providing
us the functionality to do SubResources.

Also will enable tightening up of permissions re: #150

Implement grpc-gateway in front of the gRPC based sdk-server, so that
it can be access via HTTP+JSON.

This includes documentation and a swagger/openapi specificiation.

This also has been implemented such that the sdk-server is still a single
binary, and as such, the HTTP+JSON interface can still be used for local
development.

Closes #240

This also replaces the C++ build image we have from the gRPC docker hub,
with one that we manage ourselves, since getting updates in a timely
matter was getting difficult.

The C++ base will likely go away once the transition to REST based SDK,
so the base may end up going away.

This is prerequisite for #240

Rather than a handrolled solution, this commit uses heptio's healthcheck
library. Future consumers of the health check handler need only to
register liveness or readiness probes.

Update install.yaml to use /live for liveness check.

Also, inline health handler function for consistent style.

Webhook library to make k8s webhooks easy(er) to use,
as well as setting default values on GameServers via it
for when they are first created.

Some refactoring of GameServer sync in the controller
was required and a new PortAllocation state was created.

This is also makes #70 and #10 possible to implement.

Upgraded vendored libraries and gen'd the CRD clients.
Very straight forward!

When running `kubectl describe` on GameServers, this will
now display records of major events in the lifecycle of
the GameServer.

This was setup work for reporting issue for #10 (validation)

Closes #32

Move the dependency toml to all use the release branches
of the Kubernetes libraries.

Also changes the build image to use the release-1.8 branch
of the code-generator Kuebrnetes repository, now that
it hsa vendored dependencies.

Closes #1

First implementation was done in Go as prototyping.
Implementation is done with gRPC so it should be
relatively trivial to generate new SDKs for each
language.

Implemented gRPC sidecars server to accompany the SDK
and processing of the change in states, such that the
IP and Port of the GameServer is available in the
GameServer status when its status is Ready.

Closes #16

This includes vendoring for the kubernetes controller framework, crd extensions,
our logging and error management etc.