Docker Desktop Kubernetes integration¶

Docker Desktop provides a built-in integration that allows developers to run a single-node Kubernetes cluster locally on their macOS or Windows machines^[400-devops-06-kubernetes-k8s-ithelp-day4-readme.md]. This feature is designed to provide a convenient local environment for development and testing, eliminating the need to install separate dependencies like Minikube^[400-devops-06-kubernetes-k8s-ithelp-day4-readme.md].

Installation and Setup¶

To enable the integration, users must navigate to the Settings menu within the Docker Desktop interface and check the Enable Kubernetes option^[400-devops-06-kubernetes-k8s-ithelp-day4-readme.md]. Selecting this option triggers an installation process where Docker Desktop downloads and configures the necessary container images required to run the cluster^[400-devops-06-kubernetes-k8s-ithelp-day4-readme.md].

Once the process is complete, a successful installation is indicated by a green status light for the Kubernetes Service within the GUI and the presence of running Kubernetes-related containers^[400-devops-06-kubernetes-k8s-ithelp-day4-readme.md].

Verification¶

After enabling the feature, the cluster status can be verified using the standard kubectl command-line tool^[400-devops-06-kubernetes-k8s-ithelp-day4-readme.md]. Common verification commands include:

kubectl cluster-info: Displays the cluster's connection information^[400-devops-06-kubernetes-k8s-ithelp-day4-readme.md].
kubectl get nodes: Lists the available nodes in the cluster^[400-devops-06-kubernetes-k8s-ithelp-day4-readme.md].
kubectl version --short: Outputs version information for both the client and the server^[400-devops-06-kubernetes-k8s-ithelp-day4-readme.md].

Ingress Controllers¶

The local Docker Desktop cluster supports the installation of standard Kubernetes extensions, such as the NGINX Ingress Controller^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md, 400-devops__06-Kubernetes__k8s-ingress-controller-docker-desktop__README.md]. This can be deployed to handle incoming traffic and domain name resolution for local services^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md, 400-devops__06-Kubernetes__k8s-ingress-controller-docker-desktop__README.md]. Users can install the controller using tools like Helm or by applying standard manifest YAML files^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md, 400-devops__06-Kubernetes__k8s-ingress-controller-docker-desktop__README.md].

Sources¶

^[400-devops-06-kubernetes-k8s-ithelp-day4-readme.md] ^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md] ^[400-devops__06-Kubernetes__k8s-ingress-controller-docker-desktop__README.md]