Here is the seriousness of the situation. I use profiles - like so minishift profile set demo1 minishift start # do some demo minishift stop minishift profile set demo2 minishift start # do some other demo minishift stop minishift profile set demo3 minishift start # yet other demo minishift stop # close laptop, drive/fly to next location, repeat the whole process
Yet, at the next location, I get a new IP address and the following error. This particular VM's IP was 106, yet it reverted back to 101. Caused By: Error: Get https://192.168.99.101:8443/healthz/ready: x509: certificate is valid for 10.0.2.15, 127.0.0.1, 172.17.0.1, 172.30.0.1, 192.168.99.106, not 192.168.99.101 the demos are basically: bit.ly/msa-instructions bit.ly/istio-tutorial bit.ly/faas-tutorial and you can not really run 2 of these in the same VM due to the 10 pods per core limit. minishift ip --set-static does not seem to make the IP "sticky". It really wants to go back to 100. It seems the IP address is not "stored" in the profile. So, this makes profiles essentially unusable. creation script: minishift profile set istio-tutorial minishift config set memory 8GB minishift config set cpus 3 minishift config set vm-driver virtualbox minishift config set image-caching true minishift addon enable admin-user minishift addon enable anyuid # minishift ip --set-static minishift start
_______________________________________________ Devtools mailing list Devtools@redhat.com https://www.redhat.com/mailman/listinfo/devtools
