rjmorse / kubernetes-windows-vagrant Goto Github PK

Rather than this:

Start-Job -Name kubelet {c:\k\start-kubelet.ps1 -clusterCIDR $ClusterCIDR *> c:\k\kubelet-logs.txt}
Start-Job -Name kubeproxy {c:\k\start-kubeproxy.ps1 *> c:\k\kubeproxy-logs.txt}

I'd consider trying something like WinSS. It can ensure that the processes run and it can do the log serialization - it even does log rolling to ensure you don't use too much disk space. It does it all via folder/files structure for the directories it is managing services for.

The path that is in the current Vagrantfile doesn't work:
IMAGE = "WindowsServer1709Docker"

I found this on vagrant cloud and am trying it now: symbols/windows_server_1709_docker

Here's the trail of the error:

    k-w-w1: Downloading: WindowsServer1709Docker
    k-w-w1:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

Couldn't open file /C:/dev/kubernetes-windows-vagrant/vagrant-k8s-manual/WindowsServer1709Docker

This actually is not good for folks with Windows laptops using ics over wifi with hyper-v. I personally have an Internal network rigged up with DHCP that will give outbound Internet Access. It is an "internal network"

if((Get-VMSwitch -SwitchType External).Count -lt 1)

It's easy enough not to use this, but I did spend time trying to get an external network to work until I realized that it wasn't going to.

If nothing else, maybe a comment on the line to explain that this check isn't necessary.

You can specify username/password in Vagrantfile with the following syntax:

$smb_username = "smbuser"
$smb_password = "notarealpassword"

    subconfig.vm.synced_folder "../vagrant-synced/", "/vagrant", type: "smb",
        smb_password: $smb_password, smb_username: $smb_username

I tested this with both k-builder and k-m1. The windows host is downloading now, but I expect it to work there too.

Possible implementation:
setup-enviornment.ps1 can validate that you have an smbuser.yml (added to .gitignore) and that the user is a valid admin. Then the Vagrantfile can directly load the yaml in. Technique outlined here. It's not perfect, but it's better than it is now - specifically the prompts for user/password that if you type incorrectly fails the whole thing.