From 850f421ccd455fb15d1cb158681a8a30b79f1c41 Mon Sep 17 00:00:00 2001 From: Sharif Elgamal Date: Mon, 3 Feb 2020 15:12:49 -0800 Subject: [PATCH] adding extra info for minikube start and docker-env --- .../proposed/20200130-multinode/multinode-proposal.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/enhancements/proposed/20200130-multinode/multinode-proposal.md b/enhancements/proposed/20200130-multinode/multinode-proposal.md index cc934e1e50..7370db042d 100644 --- a/enhancements/proposed/20200130-multinode/multinode-proposal.md +++ b/enhancements/proposed/20200130-multinode/multinode-proposal.md @@ -34,6 +34,14 @@ Each node will correspond to one VM (or container) and will connect back to the Also added will be the `node` sub command, e.g. `minikube node start` and `minikube node delete`. This will allow users to control their cluster however they please. Eventually, we will want to support passing in a `yaml` file into `minikube start` that defines all the nodes and their configs in one go. +Users will be able to start multinode clusters in two ways: +1. `minikube start --nodes=2` +1. * `minikube start` + * `minikube node add --name=node2` + * `minikube node start --name=node2` + +A note about `docker env`, the initial implementation won't properly support `docker env` in any consistent way, use at your own risk. The plan is to propagate any changes made to all the nodes in the cluster, with the caveat that anything that interrupts the command will cause a potentially corrupt cluster. + ## Alternatives Considered _TBD_