Set roadmap for 1.5 and 1.6 releases

[chrislovecnm]

Starting with this issue, but we need to start working on a roadmap for 1.5 and 1.6 releases. Please comment on your current needs, and we will get it into a PR for a roadmap. We will host a meetup to discuss and prioritize.

Here is the list for our first meeting:

1. Private networking Support for private subnet instance groups with NAT Gateway #428 complete
2. Improve upgrades rolling-update heuristic needs improvement #489 kops rolling-update should do a real rolling-update #37 No need to rolling-update nodes if they are already at latest #313 started
3. CNI Networks CNI networking installation support #621 complete
4. Backups and Recovery Can we back up the S3 files onto the master EBS #297 Do periodic snapshot of master volume #366
5. Improve Documentation Update README and project name #652 complete
6. Improve unit testing started
7. Implement e2e testing harness started
8. Code organization and cleanup
9. HTTP API mode - Kops API #633
10. Improve YAML and API examples
11. Setup and start using Kanban with Github
12. Cluster Validate Kops doesn't provide way to check if cluster creation completed #588 - in but has a couple of bugs
13. Protect nodes / masters from deletion.
14. API auth-mode Implement authorization-mode for kube-apiserver #312
15. Self hosting resources Self Hosting of Resources #715 channels tool should be able to use a particular context #601
16. Explicit AWS support by Kubernetes in 1.5, utilizing kops. This encompasses more work outside this repo as well.
17. Custom tags Add optional tags to AWS deployments #729
18. Process improvements, tags, PRs, the way we do stuff completed
19. @k8s-bot use em completed
20. clean house / issues Can we clean up kops issues? #640
21. more demos and examples
22. ETC and other hardening Improve etcd hardening in clustered setup #230 IAM review #376
23. Plugins model - kops allows for plugins
24. SSL improvements - bring your own keys Support real ssl certs for api server  #530
25. Terminate API servers with ELB Terminate API TLS with an ELB #234
26. 1.4 / 1.5 features Sync with 1.4 features #356
27. Remove addons manager, or replace as a plugin Stop running kube-addons-manager #385
28. Autoscaling KUBE_ENABLE_CLUSTER_AUTOSCALER using kops on AWS? #531
29. Sizing of masters and nodes Default master size is too small #728 pretty sure this is done

[chrislovecnm]

Pretty easy request #666

[jkemp101]

+1 Backups/recovery and just general disaster recovery

I would also like to see #312 added to the list to include one/both of the authorizations modes.

[chrislovecnm]

@zmerlynn any ideas?

[chrislovecnm]

@jkemp101 we already have an engineer working through the steps, and it is his desire to drop that in.

[chrislovecnm]

@jkemp101 #312 is important to us as well as we are looking at multi-homing :rimshot

[chrislovecnm]

cc: @JuJu227 @faraazkhan

[zmerlynn]

We'd like to see explicit AWS support by Kubernetes in 1.5. In order to do that, there's a few more pieces of developer efficiency that need to be done:

• PR builder for the kops repo
• PR builder on the kubernetes repo
• Submit queue blocking build

[chrislovecnm]

Another one #729 tags!!!

[krisnova]

Would like to get #640 in there tomorrow as well..

[krisnova]

Also - would it be prudent to get issues created for the topics listed above without issues? I think it would.. @chrislovecnm thoughts?

[chrislovecnm]

See Zach's comments above

[chrislovecnm]

Yaml examples and demos, @brandoncole mentioned that

[chrislovecnm]

Image road map, ami's

[krisnova]

Labels and Milestones

Can we start using them more? I added some new labels I would like to start using for PRs..

But more importantly.. milestones, and what are the thoughts there?

[chrislovecnm]

@kris-nova we need process improvements. As we talked using github kanban is duplicated work for the Datapipe folks.

[chrislovecnm]

Another one #471

[muudyguy]

Item 28 seems very critical to me. Absence of this feature forces us to have all the nodes k8s needs up and running, which means we have to pay for them even if we dont have traffic. Am I missing something, or with the current condition, it is very inefficient to have k8s up in aws ? Can someone enlighten me?

[yissachar]

@logicaleak It's not clear that this is something that kops needs to support vs you adding manually. See https://github.com/kubernetes/contrib/tree/master/cluster-autoscaler for how to add it to your cluster. It's possible that in the future kops supports easy setup via a flag, but there doesn't seem to be anything stopping you from adding it yourself.

[nicolasbelanger]

+1 for Improve upgrades #489 #37 #313

[rcruzper]

It would be great if kops could manage (add/remove) addons installed on master when the cluster is created #493

[krisnova]

@chrislovecnm @justinsb can we take this list and give this a once over? We have new versioning, and some of this needs to be updated

[chrislovecnm]

updated

[krisnova]

@chrislovecnm - Can we update the title too? I think these versions are no longer targeted

[MilanDasek]

Guys,

I would like to ask when you plan to release kops compatible with kubernetes 1.6 (March 22nd)?
We would like to upgrade our cluster from 1.5.2 to 1.6

Thank you

Milan