Variable Name | Value |
---|---|
VAGRANT_EXPERIMENTAL |
typed_triggers |
VAGRANT_SMB_USERNAME |
|
VAGRANT_SMB_PASSWORD |
<Username> (e.g. HOME\misha ) |
If VAGRANT_EXPERIMENTAL
is correctly set you will see the following at
the start of Vagrant:
==> vagrant: You have requested to enabled the experimental flag with the following features:
==> vagrant:
==> vagrant: Features: typed_triggers
==> vagrant:
==> vagrant: Please use with caution, as some of the features may not be fully
==> vagrant: functional yet.
vagrant destroy -f
vagrant up --provider=hyperv
IMPORTANT: The last step of Windows worker configuration needs: to be done manually
Login into Windows VM and in elevated Powershell execute:
cd c:\vagrant\win-worker
.\start-k8s.ps1
If Vagrant is stuck creating windows node:
-
Ctrl-C
-
Kill
ruby.exe
-
Re-provision node
vagrant up --provider=hyperv--provision win-worker-1
Reprovisioning will reapply all provisioning steps for VM (node). All provisioning steps are idempotent.
Flannel is installed in Gateway-Host mode:
networking\kube-flannel.yml
:
net-conf.json: |
{
"Network": "10.244.0.0/16",
"Backend": {
"Type": "host-gw"
}
}
Flannel daemon sets will be patched to run on Linux only by
nodes\master\node-selector-patch.yaml
:
spec:
template:
spec:
nodeSelector:
beta.kubernetes.io/os: linux
- Virtual Machines
Vagrant name | VM name | User | Password |
---|---|---|---|
master |
k8s-master |
vagrant | vagrant |
worker-1 |
k8s-worker-1 |
vagrant | vagrant |
win-worker-1 |
k8s-win-worker-1 |
Vagrant | vagrant |
- Cluster config file
config
- Cluster join instructions
kubeadm-join
- Cluster join script
kubeadm-join.sh
Create Linux pod:
$env:KUBECONFIG="..."
kubectl apply -f
Check that it is running:
kubectl get pods
Create Windows pod:
$env:KUBECONFIG="..."
kubectl apply -f
kubectl get pods