Docker for windows kubernetes taking long time to load

#Docker for windows kubernetes taking long time to load upgrade#
#Docker for windows kubernetes taking long time to load code#

This seems to be overhead of the setup on Windows. Docker run timeД®xecuting a single empty alpine container through docker run alpine echo 'test' takes roughly 2 seconds.

We would rather not introduce more complexity, though, so we have not explored this avenue any further.

#Docker for windows kubernetes taking long time to load code#

This situation can probably be improved with an alternative type of volume that enables sharing of code between deployements and jobs. Although we have not modified the whole application, initial tests indicate this is not particularly faster than the gitRepo volume. We tried replacing the gitRepo volume with a sidecar container that retrieves the application code as a TAR. Starting the environment for the first time takes over 25 minutes, restarting it takes about 20 minutes. Understandibly, this only seems to worsen the problem. Kubernetes is installed through minikube with -vm-driver none.Д¬ontrary to our local development environment, the staging environment retrieves the application code through a (deprecated) gitRepo volume for almost every deployment and job. Our staging environment consists of Ubuntu with native Docker. Some things we have discovered and tried are listed below. Running that same hook through Helm and Kubernetes regularly takes 15 seconds or more. Running a single hook manually with docker run is fast (~3 seconds). As far as I know, unchanged objects are not modified at all by Kubernetes.

#Docker for windows kubernetes taking long time to load upgrade#

Helm upgrade -force -install modules/module20/chart &Д®xecuting the same startup script again later to 'restart' the application still takes about 5 minutes. Helm upgrade -force -install modules/module01/chart & Helm upgrade -force -install modules/infrastructure/chart Any help or insights to improve the situation would be greatly appreciated.ДЄ simplified version of our startup script: #!/bin/bash We have tried to improve the (re)start time, but to no avail. This seems far to slow we are probably making an important mistake somewhere. When creating the application environment for the first time, it takes more that 20 minutes to become available.

Docker for Windows is configured to use 2 CPU cores (of 4) and 8GB RAM (of 24GB). To simplify management of our Kubernetes yaml files we use Helm 2.11.0. Altogether there are probably about 120 yaml files, which eventualy result in about 50 running pods.Дuring development we are running Docker for Windows version 2.0.0.0-beta-1-win75 with Docker 18.09.0-ce-beta1 and Kubernetes 1.10.3. Some of those jobs are defined as Helm pre-install and pre-upgrade hooks. Each module contains a (Helm) chart with several deployments, services and jobs. Our application consists of circa 20 modules.