Add simple service redirection
Update roadmap

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.
Merge pull request #1026 from lavalamp/redirect

Add simple service redirection
Fixed kubelet /healthz by using healthz package

Fixed #1094
Remove unnecessary parameter from NewRegistry
Make salt configs work with Jinja 2.6.

Fixes #1089
Merge pull request #1096 from jbeda/fix-jinja-map

Make salt configs work with Jinja 2.6.
Merge pull request #1095 from dchen1107/cleanup

Fixed kubelet /healthz by using healthz package
Merge pull request #1084 from thockin/roadmap

Roadmap Updates
Merge pull request #1097 from bcwaldon/remove-code

Remove unnecessary parameter from NewRegistry
Start scheduler locally.
Add quotes for variable; change shell redirection.
Merge pull request #1100 from ddysher/local-start-scheduler

Start scheduler locally.
Fix incorrect tag in MinionList
Fix flaky scheduler factory test.
Build tweaks

Wrap long lines.
Add GOFLAGS support to build and test.
Comments.
Merge pull request #1108 from thockin/build_cleanups

Build tweaks
Merge pull request #1104 from lavalamp/fix

Fix flaky scheduler factory test.
Merge pull request #1102 from lavalamp/fixApi

Fix incorrect tag in MinionList
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>