Road map to Stable v1.0 release

[mattma]

• Current, if you run the update-demo example in the cluster, it will work in all cases. Except that it cannot access the pod data by using API server endpoint via proxy/namespaces/default/pods/" + server.podId + "/data.json. Compare with the original update-demo in Kubernetes repo.
• Using images/containers instead of curl/wget binary. See Issue 5
• configuration instead of hard code values. See Issue 7
• User need an authentication to access the API server. via secret, ssh key, etc.
• Test in the production machines. Form a cluster, to see how it perform via kubectl command from local machine.
• Write an documentation for how to deploy to a production environment. Ex: "digitial ocean", "AWS", etc
• Three master nodes for high availabilties. Based on the design goal
• Provide an easy update path when a newer version of the kubernetes release via Environment Variable
• Current implementation of dns controller is borrowed from here. Need someone who is knowledgable on this topic to review it.
• HTTP proxy service. Do we need this proxy service?
• Do we need to have rpcbind.service and rpc-statd.service?
• Someone from In-depth kubernetes background could review all the units files.
• Support for service-account and tokens. See here

[mattma]

@yichengq I have built up a list to sum up ROAD TO 1.0. Feel free to add more. We will track them in the central place here.