Update roadmap & principles for 2020 (comments & discussion welcome!)

[tstromberg]

Q4 is about to begin, so I'm sending this out now so that we can get the comments rolling in well in advance.

We should aim for ratification before KubeCon 2019 (Nov 18).

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tstromberg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tstromberg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[medyagh]

looks good on first look.

[afbjorklund]

As I mentioned elsewhere, I would prefer not treating Docker specific to other runtimes. It is fine to have a default, but I think it should use CRI.

• VM-free deployment to Docker
• VM-free deployment to Podman

Better to say “Containers”

[blueelvis]

Looks good! I am really excited about the new features planned!

[tstromberg]

Thank you for the feedback! I am particularly curious if anyone has suggestions on:

• Any items that need clarification
• Any items that are not roadmap worthy
• Any important items that are missing from the roadmap

[blueelvis]

What does WSL2 support entail in this case? Could you please explain this more?

[afbjorklund]

I was thinking we could include running on “generic” virtual machines and even bare metal. As per the issue that I wrote (#4733)

[afbjorklund]

Thinking about how we can "expand" these ideas gradually, like how we can move them from principles to roadmap to descriptions. The current roadmap is a bit cryptic, so it would be great if it could gradually refer to a lengthier document where each item has a least a couple of sentences. But I think the length of the current documents (principles/roadmap) is just about right, so keep that!

Maybe it is enough to add a GitHub reference, but those issues tend to be added with history like discussions and revisions (and bots!) so it is harder to keep a generic summary updated there ?

Direct links:

• Principles 0836a2d

• Roadmap 0836a2d

Maybe it can be retrofitted with the MEP suggestion ? Or just add yet another markdown file. Maybe it is enough with one sub-heading per roadmap item, and just add some text. Two places to update, but...

[afbjorklund]

Graphical User Interface

I hadn't thought about this item in a long time. But when I saw the Kubernetes integration in Visual Studio Code*, I'm starting to think that it is actually quite nice to have, even if it is only "start" and "stop"...

• https://code.visualstudio.com/docs/azure/kubernetes

Started to play with Qt5, and it is lotsa fun! We should definitely at least have a small minikube icon, it doesn't look impossible when looking at https://github.com/therecipe/qt and its small systray.go* ?

• https://doc.qt.io/qt-5/qtwidgets-desktop-systray-example.html

[josedonizetti]

@tstromberg I'd like to explore the idea of using minikube for developing Kubernetes itself. Does it sound like a worthy item for the 2020 roadmap? I was actually considering writing an MEP about it.

[tstromberg]

@josedonizetti - Sounds great! I'll add it to the roadmap. I look forward to seeing the proposal.

@afbjorklund - indeed. Some inspiration for this idea has been seeing IDE integration (Cloud Code), as well as seeing folks using Docker for Desktop. Start/stop/resume/switch context from the menu bar would be killer, and not difficult to implement. There is room for more (addon selection, resource settings), but I would save it for a subsequent iteration.

I haven't explored which frameworks allow for buttons straight from the menubar, but I have noted that there are no less than 3 Go frameworks for menubar/systray based applications.

[tstromberg]

Updated: please take another look.