Probably easier to do it manually, but here's an idea to do it automatically.
Imagine you have a Vagrantfile which defines a number of nodes for your microk8s. Instead of doing the following, vagrant up node-01 ; vagrant up node-02 ; vagrant up node-03 # etc. from the host What if you could do, SEED=startup-script OUT=$(vagrant up node-01 -c "./${SEED}") OUT=$(vagrant up node-02 -c "./${OUT}") etc. (Run a command inside your VM, and save the output to a variable and then reuse it for subsequent calls). You would need to inject a startup-script inside your nodes, but then in essence you'd be writing a wrapper script which runs the "vagrant up node-X command". On Saturday, 11 April 2020 16:24:31 UTC-4, Brian Makin wrote: > > I'm setting a microk8s cluster. To join those nodes I have to run a > command on one node, then run the output of that command on another node. > How would I set this up? > > Is there a way to make one VM wait for another to come up before it starts > to come up? > ie: bring up the master, then all the client nodes? > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/44adf2cd-da89-412a-a4a1-b8311fadf32f%40googlegroups.com.