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:
Pretty easy request https://github.com/kubernetes/kops/issues/666
+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.
@zmerlynn any ideas?
@jkemp101 we already have an engineer working through the steps, and it is his desire to drop that in.
@jkemp101 https://github.com/kubernetes/kops/issues/312 is important to us as well as we are looking at multi-homing :rimshot
cc: @JuJu227 @faraazkhan
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:
kops repokubernetes repoAnother one https://github.com/kubernetes/kops/issues/729 tags!!!
Would like to get https://github.com/kubernetes/kops/issues/640 in there tomorrow as well..
Also - would it be prudent to get issues created for the topics listed above without issues? I think it would.. @chrislovecnm thoughts?
See Zach's comments above
Yaml examples and demos, @brandoncole mentioned that
Image road map, ami's
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?
@kris-nova we need process improvements. As we talked using github kanban is duplicated work for the Datapipe folks.
Another one https://github.com/kubernetes/kops/issues/471
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?
@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.
+1 for Improve upgrades #489 #37 #313
It would be great if kops could manage (add/remove) addons installed on master when the cluster is created #493
@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
updated
@chrislovecnm - Can we update the title too? I think these versions are no longer targeted
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
Most helpful comment
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