This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
Closed
Description
Is this a request for help?:
YES
Is this an ISSUE or FEATURE REQUEST? (choose one):
ISSUE I guess, it looks like a regression since it works for Kubernetes 1.8.x
What version of acs-engine?:
Version: v0.12.0
GitCommit: 1d33229
GitTreeState: clean
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes 1.9.1
What happened:
When using this Kubernetes 1.8 acs-engine orchestratorProfile, I end up with Windows Server 2016 agents having a 10.0 16299 (16299.15.amd64fre.rs3_release.170928-1534) kernel.
"orchestratorProfile": {
"orchestratorType": "Kubernetes",
"orchestratorRelease": "1.8",
"kubernetesConfig": {
"dockerEngineVersion": "17.05.*"
}
But when I use this Kubernetes 1.9 acs-engine orchestratorProfile, I end up with Windows Server 2012 (!) agents having a 6.2.09200.192 kernel.
"orchestratorProfile": {
"orchestratorType": "Kubernetes",
"orchestratorRelease": "1.9",
"kubernetesConfig": {
"dockerEngineVersion": "17.05.*"
What you expected to happen:
Getting Windows Server 2016 agents on Kubernetes 1.9 like I did with Kubernetes 1.8.
How to reproduce it (as minimally and precisely as possible):
1. Deploy this acs-engine template:
{
"apiVersion": "vlabs",
"properties": {
"orchestratorProfile": {
"orchestratorType": "Kubernetes",
"orchestratorRelease": "1.8",
"kubernetesConfig": {
"dockerEngineVersion": "17.05.*"
}
},
"masterProfile": {
"count": 1,
"dnsPrefix": "k8s-sl31061",
"vmSize": "Standard_D2s_v3"
},
"agentPoolProfiles": [
{
"name": "linuxpool1",
"count": 1,
"vmSize": "Standard_D2s_v3",
"storageProfile": "ManagedDisks",
"availabilityProfile": "AvailabilitySet",
"osType": "Linux"
},
{
"name": "windowspool1",
"count": 1,
"vmSize": "Standard_D2s_v3",
"storageProfile": "ManagedDisks",
"OSDiskSizeGB": 100,
"availabilityProfile": "AvailabilitySet",
"osType": "Windows"
}
],
"linuxProfile": {
"adminUsername": "[REDACTED]",
"ssh": {
"publicKeys": [
{
"keyData": "ssh-rsa [REDACTED]"
}
]
}
},
"windowsProfile": {
"adminUsername": "[REDACTED]",
"adminPassword": "[REDACTED]"
},
"servicePrincipalProfile": {
"clientId": "[REDACTED]",
"secret": "[REDACTED]"
}
}
}
2. You get Windows Server 2016 agents:
$ kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
37061k8s9010 Ready <none> 16m v1.8.6-21+aad85df0a0abed-dirty <none> <unknown> 10.0 16299 (16299.15.amd64fre.rs3_release.170928-1534) docker://17.6.2
k8s-linuxpool1-37061256-0 Ready agent 20m v1.8.6 <none> Debian GNU/Linux 8 (jessie) 4.11.0-1016-azure docker://17.5.0
k8s-master-37061256-0 Ready master 20m v1.8.6 <none> Debian GNU/Linux 8 (jessie) 4.11.0-1016-azure docker://17.5.0
3. Deploy this acs-engine template:
{
"apiVersion": "vlabs",
"properties": {
"orchestratorProfile": {
"orchestratorType": "Kubernetes",
"orchestratorRelease": "1.9",
"kubernetesConfig": {
"dockerEngineVersion": "17.05.*"
}
},
"masterProfile": {
"count": 1,
"dnsPrefix": "k8s-sl31062",
"vmSize": "Standard_D2s_v3"
},
"agentPoolProfiles": [
{
"name": "linuxpool1",
"count": 1,
"vmSize": "Standard_D2s_v3",
"storageProfile": "ManagedDisks",
"availabilityProfile": "AvailabilitySet",
"osType": "Linux"
},
{
"name": "windowspool1",
"count": 1,
"vmSize": "Standard_D2s_v3",
"storageProfile": "ManagedDisks",
"OSDiskSizeGB": 100,
"availabilityProfile": "AvailabilitySet",
"osType": "Windows"
}
],
"linuxProfile": {
"adminUsername": "[REDACTED]",
"ssh": {
"publicKeys": [
{
"keyData": "ssh-rsa [REDACTED]"
}
]
}
},
"windowsProfile": {
"adminUsername": "[REDACTED]",
"adminPassword": "[REDACTED]"
},
"servicePrincipalProfile": {
"clientId": "[REDACTED]",
"secret": "[REDACTED]"
}
}
}
4. You get Windows Server 2012 agents:
$ kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
30771k8s9010 Ready <none> 23s v1.9.1 <none> Windows Server Datacenter 6.2.09200.192 docker://17.6.2
k8s-linuxpool1-30771201-0 NotReady agent 4m v1.9.1 <none> Debian GNU/Linux 9 (stretch) 4.11.0-1016-azure docker://17.5.0
k8s-master-30771201-0 NotReady master 4m v1.9.1 <none> Debian GNU/Linux 9 (stretch) 4.11.0-1016-azure docker://17.5.0
Anything else we need to know:
Activity