Roadmap: Bring back Kubernetes on/off toggle in menu

Created on 25 Aug 2020 · 6Comments · Source: docker/roadmap

Tell us about your request
Having K8s in DD is great, but we don't always need it on, and to save CPU and Battery, I always disable it when not needed. There used to be a enable/disable toggle in the Kubernetes sub-menu of the Docker Desktop icon. At some point, it went away. I'm asking for it back!

Which service(s) is this request for?
Docker Desktop

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Quickly enable/disable Kubernetes in 2-clicks rather than 6+ (the current process).

Additional context
BONUS: I've met many people who have Docker Desktop installed but don't realize it can install and manage a K8s instance (I guess they never dug through the settings). To be honest, it's weird that a big feature of a product is hidden in settings anyway, so bringing this enable/disable to the main menu as a first-class option might reveal it to those that didn't know it was there all along.
It should also be in the new Desktop GUI. If K8s isn't enabled, it should list it as "Enable Kubernetes" at the bottom. If it's running, it should have a button to "suspend" or "disable" it.

community_new docker_desktop

Source

BretFisher

👍10 👀2

All 6 comments

To me this is related to #68. If we can quickly toggle K8s on and off, it will help offset the cpu/battery costs of leaving Docker Desktop running.

BretFisher on 27 Aug 2020

👍1

People installed Docker Desktop also seamless installed Swarm because Docker spec has been already merged with swarm spec.
Everybody can see that the Docker context has a mandatory attribute Orchestration engine. Actually, docker is always installed with some orchestration engine and up to "manager" to decide which of the engines is activated and in use. The switch is on/off, mutually exclusive. The current menu with the single checkbox simply reflects a stage in the product evolution.
Every orchestration comes with its Management GUI, mostly 3rd party. This proposal means "Add some UI elements in educational purposes", but has very low practical value. When Kubernetes is enabled user has to select context - it is impossible without certain education too. The UI is going to be more and more complex and inconsistent.
Are there some figures which prove that Kubernetes or Swarm stack consumes some CPU or battery capacity when it is idle exist? I believe that it is only a memory consumption issue.
When Docker Desktop is running on Windows Home with only 8Gb memory any orchestration is impossible because of machine has not enough resources - any UI is redundant.

PavelSosin-320 on 27 Aug 2020

P.S. If you really have problems with CPU temperature or battery usage related to Docker desktop orchestration, please attach a screenshot of Resource monitor and powercfg /batteryreport

PavelSosin-320 on 27 Aug 2020

👎1

@BretFisher what about having a Desktop CLI where we had the ability to enable/disable Kube directly? Would this be better or would you still feel the need for both? And if so why :D

nebuk89 on 10 Sep 2020

👍1

I think either is fine for me, but a GUI option seems the most logical for
the community at large.

On Thu, Sep 10, 2020 at 10:37 AM Ben De St Paer-Gotch <
[email protected]> wrote:

@BretFisher https://github.com/BretFisher what about having a Desktop
CLI where we had the ability to enable/disable Kube directly? Would this be
better or would you still feel the need for both? And if so why :D

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/roadmap/issues/149#issuecomment-690332426, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGBNX2FIVMQMXTM4LW2DD3SFDQCDANCNFSM4QLECGMA
.

BretFisher on 10 Sep 2020

👍1

To me this is related to #68. If we can quickly toggle K8s on and off, it will help offset the cpu/battery costs of leaving Docker Desktop running.

Absolutely "quick" is the operative word as it often takes minutes to wait for startup when I just want to nuke the k8s cluster or reset it and I have to wait for a full start and then it has to restart with or without it... and I've found even with the preferences toggle off if I had it on in the past I might have an old cluster lingering on an old device but somehow in updating the checkbox is unchecked so I have to check -> restart DD -> reset -> restart DD (and/or uncheck k8s -> restart) and it's all super painful... then again when I want it, it would be nice to quickly request that and even if it took time and crunched away at least I'm not waiting to complete said intermediate steps