Containers on Azure Container Service and related issues
Hi I recently create a k8s cluster on Azure Container Service, just wonder if the containers (pods) created are all hyper-V containers?
As an aside, I found that every time I do "kubectl create -f file" to start the windows container (pods), it takes almost 2 mins to pull the image and then turning the state of the pods from "Creating Container" to "Ready". Is it normal?? If not, are there any suggestions to speed up this process? Seems now the k8s cluster is pulling image each time even if the image is the same. Note that I am now using the windows server core image which I find the size is indeed quite big (>9GB).
Similar Questions
1 Answer
just wonder if the containers (pods) created are all hyper-V containers?
Do you mean create pods in K8S, will k8s create k8s containers to all nodes?
If I understand it correctly, the answer is yes. We can create pods to one node or multiple nodes.
If we create pod to one node, like this: 
it takes almost 2 mins to pull the image and then turning the state of the pods from "Creating Container" to "Ready". Is it normal?
There are multiple reasons will effect that speed, I think it is normal.
For example, you create pod1 in node1, node1 will pull the image from the registry. Then you create another pod (pod2) on node2, K8S will pull image from the registry too.
By the way, it seems K8S can't create container with image which store in master or nodes. Only work with registry, please refer to this case.