Alex Chesser

Be careful not to solve via brute force. Make sure you use a hash table.

https://jobs.netflix.com/culture

manual steps to fix comment out Vagrantfile lines 16, 17, 18 requirement - Git SCM with UNIX TOOLS options added to the math set system environment variable OPENSSL_CONF=C:\Program Files (x86)\Git\ssl\openssl.cnf...

changed tactics from above. ssl certificate above created successfully - open git bash - change directoy to /c/www/coreos-kubernetes/single-node - edit file `../lib/init-ssl` change line 5 to `OPENSSL="openssl"` (open ssl available...

edit line 70 of `../lib/init-ssl` add additional forward slash character in front of "/CN ``` $OPENSSL req -new -key "$KEYFILE" -out "$CSRFILE" -subj "//CN=$CN" -config "$CONFIGFILE" ```

after re running the `init-ssl` commands above with corrected script `vagrant up` works in powershell on windows. there may be ways to improve this a little.

I've started tracking the steps required to make this work as expected in a branch. With the steps found here: https://github.com/AlexChesser/coreos-kubernetes/commit/64286a154a5a10a384a119fb88abb4253b872cd7 I am able to get further in the machine...

VirtualBox 5+ worked with vagrant up. next steps: ``` PS C:\www\coreos-kubernetes\single-node> vagrant up PS C:\www\coreos-kubernetes\single-node> vagrant ssh CoreOS alpha (845.0.0) core@localhost ~ $ curl -L -O https://github.com/kubernetes/kubernetes/releases/download/v1.1.2/kubernetes.tar.gz core@localhost ~ $...

Hi @aaronlevy Indeed I did get this working in windows, but haven't gone so far as to make it work "cross-platform" or automatically. Like @huangsam says, I made the same...

Hey @geekkean - sorry I haven't tried multinode.