Signed-off-by: Vojtech Vitek (V-Teq) <vvitek@redhat.com>

Fix pod status error with List method.

Add initial resources.md for discussion

Fixed annoying typo

Tweaks to reflect comments from thockin

Anoying typo fixed

Add a Makefile

Invert api and api/v1beta1 dependencies

This is a very simple Makefile that just passes through to the current hack/*
scripts.  Only "make", "make test", and "make clean" are supported for now.

Make `godep go build ./...` work

This makes `godep go build ./...` work.

go build ./... will ignore any directory starting with an underscore.

Describe some ecosystem projects around Kube

Add the resource version to api.*List items from etcd

This is some cleanup that has been needed for a while.
There's still one more step that could usefully be done, which is to
split up our api package into the part that provides the helper
functions and the part that provides the internal types. That can come
later.

The v1beta1 package is now a good example of what an api plugin should
do to version its types.

Remove workaround for salt-minion startup in vagrant/provision-minion.sh

The workaround was not needed, as salt-minion was always correctly
started in the Vagrant minion setup.

The issue reported in #270 was clearly specific do System V style init
scripts and will not affect systemd.

Also remove the inaccurate comment from provision-master.sh, since -X
was not even really in use there.

Tested:
- Performed 3 full `vagrant up` and `vagrant destroy -f` cycles with at
  least 3 minions and up to 6 minions in one case. Checked that
  salt-minion was up in each of the minions using a `systemctl status
  salt-minion` command.
- Started nginx on the cluster using cluster/kubecfg.sh, confirmed it
  was up with `list /pods` and confirmed it was reachable using wget on
  port 8080 of the minions.
Signed-off-by: Filipe Brandenburger <filbranden@google.com>

Fix incorrect tag in MinionList

Fix flaky scheduler factory test.

Build tweaks

Wrap long lines.
Add GOFLAGS support to build and test.
Comments.

Allows clients to watch more easily (can invoke Get, then
Watch).

Start scheduler locally.

Remove unnecessary parameter from NewRegistry

Roadmap Updates

Fixed kubelet /healthz by using healthz package

Make salt configs work with Jinja 2.6.

Fixes #1089

Fixed #1094

Add simple service redirection

We took a hard look at 1.0 and what things ae really REQUIRED to get to a
stable release that is "useful".  This required moving some things we thought
were really important but not CRITICAL down the list.

For now they are stricken from this doc, but I expect this doc to start
growing a "post 1.0" list soon.

Things stricken and why:

Using the host network: This is primarily a performance optimization, but it
causes potential problems with other uses of HostPorts.  We'd rather focus on
fixing perf problems than dodging them.  We can revisit later if there is a
strong case for it.

Representation of Ports in the Manifest structure: We discussed and decided
that, since HostPort semantics have changed, this matters less than before.

Scenarios where IP-per-pod is hard or impossible: We're still game to help
people figure out how to make it work, but we don't see a case for making k8s
1.0 work in a fundamentally different mode.  Too much churn and risk.  We can
revisit later, if needed.

Auto-scaling controller: We really want this, but it's not critical to making
k8s "useful".

Pluggable authentication: Overlaps with the other identity topic.  Having one
topic seems clearer.

Pod spreading: We still want this, but it's not critical for 1.0.

Container status snippets: We still want this, but it's not critical for 1.0.

Docker-daemon-kills-all-children-on-exit problem: This is still a big problem,
but we're not going to gate our 1.0 on something we don't control.  This has
to be documented as a shortcoming in general.

Interconnection of services: expand / decompose the service pattern: overlaps
with the other services topic.

Recipes for settings where networking is not like GCE: This is happening in
the form of cloudprovider modules, but is not going to gate 1.0.

Client should validate the incoming host value