This is a brief brain-dump of the investigations I've done into how to make Kubernetes easier to setup along with some options suggested by others in SIG-Windows.
- aks-engine set precedence of putting things in
c:\k
. Is that the best decision? Should executables, logs and config be separated and ACLd more strongly?
Options:
- MSI - would need to be built along with binaries. Not useful for configuration management & transitions though
- PowerShell OneGet Provider - similar to what's done for Docker. Would find right URL and download kubernetes-node-...tgz, then extract it to the right location
Setup steps:
- expand archive
- register service
- issue: logs? if kubelet doesn't start, how to troubleshoot it
kubeadm
- issue: uses Linuxy paths and creates files under
c:\var
andc:\etc
- issue: adds Linux-only kubelet parameters
- Possible solution: Ansible
- Possible solution: PowerShell DSC partial config
- Possible solution: Chef
- Possible solution: Puppet
- Possible solution: Vagrant