Closed jwalker343 closed 5 years ago
Linux Containers run fine:
Normal Scheduled 23s default-scheduler Successfully assigned scratch-dep-1136686056-xjpdv to k8s-linuxpool1-40233731-0
Normal SuccessfulMountVolume 23s kubelet, k8s-linuxpool1-40233731-0 MountVolume.SetUp succeeded for volume "default-token-14lt1"
Normal Pulling 22s kubelet, k8s-linuxpool1-40233731-0 pulling image "nginx"
Normal Pulled 18s kubelet, k8s-linuxpool1-40233731-0 Successfully pulled image "nginx"
Normal Created 17s kubelet, k8s-linuxpool1-40233731-0 Created container
Normal Started 17s kubelet, k8s-linuxpool1-40233731-0 Started container
I regressed and used acs-engine version v0.9.1 and I'm at least able to run pods
./acs-engine version
Version: v0.9.1
GitCommit: f9d0e574
GitTreeState: clean
I tested the custom VNET for Windows nodes with the snapshot 12d7fc5a8143866f34c3c6a21b003eb96960b68b from 2018-01-09. I patched the generated azuredeploy.json file, so that it contains a variable subnet with the value of the subnet range of my custom VNET like this:
"subnet": "10.1.0.0/16"
The deployment worked and the Windows nodes were successfully created. I could deploy Windows containers. But inside the Windows pods, there was a problem with DNS: I could not resolve domain names, that is, I could not reach services inside my cluster.
@chweidling I have not rebuilt a cluster using the latest snapshot, however according to https://github.com/Azure/acs-engine/issues/558#issuecomment-350348512 you may just have to wait a little while and DNS may resolve itself?
The problem does not disapper even after one hour waiting.
Hi @jwalker343 , we are facing similar issue, are you able to find root cause or solution for same.
I am facing problems deploying a hybrid cluster in custom vnet.
Error: The template parameter 'masterSubnet' is not found. acs-engine version: v0.21.2 k8s version: 1.11
Any idea when support for "Hybrid Cluster with Custom Vnet" will be added?
I was able to successfully deploy a Hybrid cluster in a custom vnet with 0.25.3. This is an old issue and is almost 1year old, so I'm marking it closed.
Is this a request for help?:
YES
Is this an ISSUE or FEATURE REQUEST? (choose one):
ISSUE
What version of acs-engine?:
0.11.0
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm) kubernetes 1.7.9
What happened: I downloaded the latest release of acs-engine and created a hybrid cluster in a custom vnet with the template below. Windows Pods fail to start with an "Error Syncing Pod"
What you expected to happen: Windows Pods should run properly.
How to reproduce it (as minimally and precisely as possible):
I have a vnet
VN-Sandbox1-useast
with 3 subnets:k8smaster = 10.201.150.0/26
k8sagent = 10.201.155.0/26
k8sclustersubnet = 10.201.240.0/21
template.json:
Run
./acsengine generate template.json
Edit the azuredeploy.json file and add the subnet variable due to https://github.com/Azure/acs-engine/issues/1767#issuecomment-345283959
Run
az group deployment create --template-file "azuredeploy.json" --parameters "azuredeploy.parameters.json" -g RG-Sandbox1-useast -n VN-Sandbox1-useast
Update route tables:
az network vnet subnet update -n k8smaster -g RG-Sandbox1-useast --vnet-name VN-sandbox1-useast --route-table <RT_NAME>
az network vnet subnet update -n k8sagent -g RG-Sandbox1-useast --vnet-name VN-Sandbox1-useast --route-table <RT_NAME>
Run a standard aspnet image:
Anything else we need to know:
C:\k\kubelet.log
kubelet.err.log
I've tried this also with
"networkPolicy": "azure"
and I get the same result. Please let me know if you need any more information.