Browse Source

scripts.nix: Use the kvm2 backend for whcluster/whremote

This commit works around pod name resolution issues under tilt with minikube.

Change-Id: I5fe6acf5f739633b5dcb57f814fd29084a359a8f
Stan Drozd 4 years ago
parent
commit
8b5e82df1b
1 changed files with 2 additions and 2 deletions
  1. 2 2
      nix/scripts.nix

+ 2 - 2
nix/scripts.nix

@@ -6,7 +6,7 @@ final: prev: {
   # * Docker supports BuildKit
   whcluster = final.writeShellScriptBin "whcluster" ''
     set -e
-    default_minikube_args="--cpus=10 --memory=10gb --disk-size=200gb"
+    default_minikube_args="--cpus=10 --memory=10gb --disk-size=200gb --driver=kvm2"
     export MINIKUBE_ARGS=''${MINIKUBE_ARGS:-$default_minikube_args}
     ${final.minikube}/bin/minikube start $MINIKUBE_ARGS
     ${final.whinotify}/bin/whinotify
@@ -53,7 +53,7 @@ final: prev: {
     ${final.mutagen}/bin/mutagen sync flush whremote-sync
 
     # Use larger cpu-count and memory values on the remote
-    export MINIKUBE_ARGS=''${MINIKUBE_ARGS:='--cpus=30 --memory=110g --disk-size=1000gb'}
+    export MINIKUBE_ARGS=''${MINIKUBE_ARGS:='--cpus=30 --memory=110g --disk-size=500gb --driver=kvm2'}
 
     # Set up/update the remote minikube cluster with whcluster
     ssh $remote_machine \