Piotr Bryk

+1 - this is also a problem for our parallel build pipeline

> This is a feature request, a bit on the advanced side. I know it's not going to make it into 1.1. Feel free to defer it or close it...

@janetkuo Should it be implemented in the UI codebase? I'm not sure. If that's behavior users expect, this should be part of spec and be in the API server. Otherwise,...

@mhenc

But for stateful set the pods are picked. And anyway, implementing such logic is kubectl should not be the way to go. Look at kubectl rolling-update for replication controllers. Its...

The use case is for users that want to try out the UI for the first time. The "paste this into your terminal" command can be called "install and launch"...

I'd assume that the user has kubectl configured first. It'd be much easier. We could use minikube to start a cluster in the v2 version. What do you think?

Yeah, something like this, but a bit more interactive and clever. I.e., open the UI when you have kubectl and UI already configured. I'll propose something over the weekend.

@codegoblins Sounds just about right. I think if you have spare cycles, it is ready to be implemented. We've been planning such feature anyways :) Are you taking this?

Hmm... I don't think this has been scoped out yet. We need a proposal and discussion on how it is going to actually work :)