# - print the pod(s) status, that matches selector 'app: myapp', in 'test' ns, using 'describe', continuouslyДocker cp. # - apply Kube deployment 'myapp.yaml', present within the CWD files # - create 'secret' Kubernetes object, with the name 'mysecret', containing the key 'access-key' with value taken from STDIN, environment var 'MY_KEY' # - apply the configMap object from the 'python-config.yaml' file, present within the CWD files # - build the image, and it's auto stored in the in-cluster daemon # - export the environment variables from the '.env' file, present within the CWD files, using 'set -a &. # - point your terminal to use the in-cluster Docker daemon, used by 'minikube' and 'kubectl' (inside 'kubemini' container) # - copy all files from CWD (in local Host) to the /home/myuser/src/ (from inside the 'kubemini' container) # Build&Deploy (+secret) from files in CWD: # Print the particular pod(s) logs (describe) constantly, under ns 'test' that matches selector '=':ДЇor (( )) | tee -a system.log' # Print all pods running in the namespace 'test': # List the Docker images present inside the in-cluster Docker daemon (docker-env), used by 'minikube' and 'kubectl':Д®val $(minikube docker-env) & docker images # Administer | Stream the 'system' logs, including 'minikube'-specific startup logs: tail -f system.log (OPTIONAL/DEBUGGING) Use the following commands to display the respected output: # //// (From Inside the nested Kubernetes cluster) Administer + Deployment | General commands | Must be executed under 'myuser' user ('su myuser') \\ However, it is recommended to consult official release notes from the Docker and the 'Tested environments' section. (OPTIONAL) It is possible to change the hardcoded 1.18.0 version of the Kubernetes Server and 'kubectl' by modifying the Dockerfile (OPTIONAL) It is possible to change the hardcoded 20.10.0 version of the Docker Engine that was being used as the main runtime by modifying theДockerfile's line 15, 'COPY -from=docker:20.10.0'. # run, non-interactive, all done automaticallyДocker run -d -it -privileged -name kubemini kubemini On the local Host, from the root of the project directory, execute the following commands to build and run the image : Minikube start -vm-driver=docker -cpus 8 -memory 4000 -kubernetes-version=1.18.0 -addons metrics-server Accordingly, please adjust the number in 'Dockerfile' to reflect the target Host's Docker settings in terms of memory and CPU allocation: Note that if the number of (v)CPUs available to the Docker engine on the Host itself is less than eight, the Kubernetes cluster inside the created docker container will not start. (REQUIRED) The following command was being used to start the Kubernetes cluster using the 'minikube' tool, which has a parameter '-cpus 8', hardcoded. (REQUIRED) Internet Access to the sites docker.io,, from the local Host on which this docker container will be hosted (REQUIRED) Installed Docker Engine and Docker CLI (Any OS) on the local Host on which this docker container will be hosted Kubernetes cluster startup, via 'minikube', +'metrics-server', +ready for 'kubectl' deployment: 3-4 minutes on average.Some key performance indicators of the setup (baselined on my home network connection): In-cluster Docker daemon (accessible via 'minikube docker-env') as the primary image registry.Docker as a primary container engine for the cluster.

Kubernetes cluster, inside the Docker container, created via 'minikube' tool.

Docker and kubernetes tool