Now we can check, if application was deployed correctly: Kubectl create -f croc-hunter.yaml -save-config apiVersion: v1 kind: Service metadata: name: croc-hunter labels: component: croc-hunter spec: ports: - port: 8080 targetPort: 8080 selector: component: croc-hunter type: "ClusterIP" - apiVersion: extensions/v1beta1 kind: Deployment metadata: name: croc-hunter labels: component: croc-hunter spec: replicas: 1 strategy: type: RollingUpdate selector: matchLabels: component: "croc-hunter" template: metadata: labels: component: "croc-hunter" spec: containers: - name: croc-hunter image: "voronenko/docker-sample-image:47372c4" imagePullPolicy: "Always" ports: - name: http containerPort: 8080 resources: requests: cpu: "10m" memory: "128Mi" livenessProbe: httpGet: path: /healthz port: http readinessProbe: httpGet: path: /healthz port: httpĪnd ingress to it apiVersion: extensions/v1beta1
Now lets test deploy CrocoHunter application Now you can run kubectl proxy in some console, and also some better control over kubernetes cluster, accessible on Get admin rights from the start : kubectl create -f k8s/dashboard-admin.yaml where dashboard-admin.yaml is apiVersion: /v1beta1 kind: ClusterRoleBinding metadata: name: kubernetes-dashboard labels: k8s-app: kubernetes-dashboard roleRef: apiGroup: kind: ClusterRole name: cluster-admin subjects: - kind: ServiceAccount name: kubernetes-dashboard namespace: kube-system New release of dashboard comes with RBAC as a default, but for that specific case we can go on a simplier setup, and
DOCKER FOR WINDOWS KUBERNETES DASHBOARD INSTALL
Lets test install kubernetes dashboard, because docker for windows provides no specific UI for that part kubectl apply -f Įcho kubectl create -f k8s/dashboard-admin.yaml What you need - is to replicate config on your linux box, and tune server address to external interface address of your box.Īfter that, you can see the context on your linux box kubectxĪnd control it using native kubectl tool kubectl get pods Server: name: docker-for-desktop-clusterĬurrent-context: docker-for-desktop-cluster Netsh interface portproxy add v4tov4 listenport=6445 connectaddress=127.0.0.1 connectport=6445 listenaddress=%EXTERNAL_IP% protocol=tcpĪccessing your cluster with kubectl from your linux machine:īy default docker patches your windows kube config with changes similar to below: apiVersion: v1 1 connectport= 2375 listenaddress= %EXTERNAL_IP% protocol=tcp Netsh interface portproxy add v4tov4 listenport= 2375 connectaddress= 127.
Has made things even more interesting - Docker for windows now is capable to run single node Kubernetes 1.1xĬluster, which you can use for your experiments as well.Įven if Windows has WSL, it still does not behave in a way how my usual linux workplace does, thus on my local lab first (note: insecure) step I do - is exposing my windows kubernetes and docker ports to my linux notebookĮxpose docker tcp daemon on 2375 SET EXTERNAL_IP= 192. So far I was using it to offload docker builds and use some VMs on a hyperV. I am a linux guy, but one of my work boxes is Intel NUC under windows with quite good memory specs.
0 kommentar(er)
