{"id":1657,"date":"2020-05-27T15:56:36","date_gmt":"2020-05-27T20:56:36","guid":{"rendered":"https:\/\/blog.iqonda.net\/?p=1657"},"modified":"2020-11-09T13:20:23","modified_gmt":"2020-11-09T19:20:23","slug":"kubernetes-development-with-microk8s","status":"publish","type":"post","link":"https:\/\/blog.ls-al.com\/kubernetes-development-with-microk8s\/","title":{"rendered":"Kubernetes Development with MicroK8s"},"content":{"rendered":"<p>Using Ubuntu's MicroK8s Kubernetes environment to test a Nginx container with a NodePort and also Ingress so we can access from another machine.<\/p>\n<h2>install<\/h2>\n<pre><code class=\"language-bash\">$ sudo snap install microk8s --classic\nmicrok8s v1.18.2 from Canonical\u2713 installed\n\n$ sudo usermod -a -G microk8s rrosso\n\n$ microk8s.kubectl get all --all-namespaces\nNAMESPACE   NAME                 TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)   AGE\ndefault     service\/kubernetes   ClusterIP   10.152.183.1   <none>        443\/TCP   2m29s\n\n$\u00a0microk8s.kubectl get nodes\nNAME      STATUS   ROLES    AGE   VERSION\nserver1   Ready    <none>   3m    v1.18.2-41+b5cdb79a4060a3\n\n$ microk8s.enable dns dashboard\n...\n\n$ watch microk8s.kubectl get all --all-namespaces<\/code><\/pre>\n<p>NOTE: alias the command<\/p>\n<pre><code class=\"language-bash\">$\u00a0sudo snap alias microk8s.kubectl kubectl\nAdded:\n  - microk8s.kubectl as kubectl<\/code><\/pre>\n<h2>nginx first attempt<\/h2>\n<pre><code class=\"language-bash\">$\u00a0kubectl create deployment nginx --image=nginx\ndeployment.apps\/nginx created\n\n$\u00a0kubectl get deployments\nNAME    READY   UP-TO-DATE   AVAILABLE   AGE\nnginx   1\/1     1            1           9s\n\n$\u00a0kubectl get pods\nNAME                    READY   STATUS    RESTARTS   AGE\n\nnginx-f89759699-jnlng   1\/1     Running   0          15s\n\n$\u00a0kubectl get all --all-namespaces\n\nNAMESPACE     NAME                                                  READY   STATUS    RESTARTS   AGE\ndefault       pod\/nginx-f89759699-jnlng                             1\/1     Running   0          31s\n...\nNAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                  AGE\ndefault       service\/kubernetes                  ClusterIP   10.152.183.1     <none>        443\/TCP                  94m\n...\nNAMESPACE     NAME                                             READY   UP-TO-DATE   AVAILABLE   AGE\ndefault       deployment.apps\/nginx                            1\/1     1            1           31s\nkube-system   deployment.apps\/coredns                          1\/1     1            1           90m\n...\n\nNAMESPACE     NAME                                                        DESIRED   CURRENT   READY   AGE\ndefault       replicaset.apps\/nginx-f89759699                             1         1         1       31s\nkube-system   replicaset.apps\/coredns-588fd544bf                          1         1         1       90m\n...\n\n$\u00a0kubectl get all --all-namespaces\nNAMESPACE     NAME                                                  READY   STATUS    RESTARTS   AGE\ndefault       pod\/nginx-f89759699-jnlng                             1\/1     Running   0          2m38s\n...\nNAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                  AGE\n...\nNAMESPACE     NAME                                             READY   UP-TO-DATE   AVAILABLE   AGE\ndefault       deployment.apps\/nginx                            1\/1     1            1           2m38s\n\nNAMESPACE     NAME                                                        DESIRED   CURRENT   READY   AGE\ndefault       replicaset.apps\/nginx-f89759699                             1         1         1       2m38s\n...\n\n$\u00a0wget 10.152.183.151\n--2020-05-25 14:26:14--  http:\/\/10.152.183.151\/\nConnecting to 10.152.183.151:80... connected.\nHTTP request sent, awaiting response... 404 Not Found\n2020-05-25 14:26:14 ERROR 404: Not Found.\n\n$\u00a0kubectl get deployments\nNAME    READY   UP-TO-DATE   AVAILABLE   AGE\nnginx   1\/1     1            1           3m40s\n\n$\u00a0kubectl get pods\nNAME                    READY   STATUS    RESTARTS   AGE\nnginx-f89759699-jnlng   1\/1     Running   0          3m46s\n\n$\u00a0microk8s.kubectl expose deployment nginx --port 80 --target-port 80 --type ClusterIP --selector=run=nginx --name nginx\nservice\/nginx exposed\n\n$ microk8s.kubectl get all\nNAME                        READY   STATUS    RESTARTS   AGE\npod\/nginx-f89759699-jnlng   1\/1     Running   0          9m29s\n\nNAME                 TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE\nservice\/kubernetes   ClusterIP   10.152.183.1    <none>        443\/TCP   103m\nservice\/nginx        ClusterIP   10.152.183.55   <none>        80\/TCP    3m55s\n\nNAME                    READY   UP-TO-DATE   AVAILABLE   AGE\ndeployment.apps\/nginx   1\/1     1            1           9m29s\n\nNAME                              DESIRED   CURRENT   READY   AGE\nreplicaset.apps\/nginx-f89759699   1         1         1       9m29s\n\n$ wget 10.152.183.55\n--2020-05-25 14:33:02--  http:\/\/10.152.183.55\/\nConnecting to 10.152.183.55:80... failed: Connection refused.<\/code><\/pre>\n<p>NOTE: Kubernetes does not provide a loadbalancer. It is assumed that loadbalancers are an external component. MicroK8s is not shipping any loadbalancer but even if it did there would not have been any nodes to balance load over. There is only one node so if you want to expose a service you should use the NodePort service type.<br \/>\nThere is no external LB shipping with MicroK8s, therefore there is no way to appoint an (LB provided) external IP to a service. What you can do is to expose a service to a host's port using NodePort.<\/p>\n<h2>nginx attempt 2<\/h2>\n<pre><code class=\"language-bash\">$\u00a0kubectl delete services nginx-service\nservice \"nginx-service\" deleted\n\n$\u00a0kubectl delete deployment nginx\ndeployment.apps \"nginx\" deleted\n\n$\u00a0kubectl create deployment nginx --image=nginx\ndeployment.apps\/nginx created\n\n$\u00a0kubectl expose deployment nginx --type NodePort --port=80 --name nginx-service\nservice\/nginx-service exposed\n\n$\u00a0kubectl get all\nNAME                        READY   STATUS    RESTARTS   AGE\npod\/nginx-f89759699-jr4gz   1\/1     Running   0          23s\n\nNAME                    TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE\nservice\/kubernetes      ClusterIP   10.152.183.1     <none>        443\/TCP        19h\nservice\/nginx-service   NodePort    10.152.183.229   <none>        80:30856\/TCP   10s\n\nNAME                    READY   UP-TO-DATE   AVAILABLE   AGE\ndeployment.apps\/nginx   1\/1     1            1           23s\n\nNAME                              DESIRED   CURRENT   READY   AGE\nreplicaset.apps\/nginx-f89759699   1         1         1       23s\n\n$\u00a0wget 10.152.183.229\nConnecting to 10.152.183.229:80... connected.\nHTTP request sent, awaiting response... 200 OK\n2020-05-26 08:05:22 (150 MB\/s) - \u2018index.html\u2019 saved [612\/612]<\/code><\/pre>\n<h2>ingress<\/h2>\n<pre><code class=\"language-bash\">$\u00a0cat ingress-nginx.yaml \napiVersion: networking.k8s.io\/v1beta1\nkind: Ingress\nmetadata:\n  name: http-ingress\nspec:\n  rules:\n  - http:\n      paths:\n      - path: \/\n        backend:\n          serviceName: nginx-service\n          servicePort: 80\n\n$ kubectl apply -f ingress-nginx.yaml \ningress.networking.k8s.io\/http-ingress created<\/code><\/pre>\n<p>NOTE: <a href=\"https:\/\/192.168.1.112\/\">https:\/\/192.168.1.112\/<\/a> pulls up Nginx homepage<\/p>\n<h2>after reboot:<\/h2>\n<ul>\n<li>grafana console works<br \/>\n<a href=\"https:\/\/192.168.1.112:16443\/api\/v1\/namespaces\/kube-system\/services\/monitoring-grafana\/proxy\/?orgId=1\">https:\/\/192.168.1.112:16443\/api\/v1\/namespaces\/kube-system\/services\/monitoring-grafana\/proxy\/?orgId=1<\/a><\/li>\n<li>ingress for nginx container works<br \/>\n<a href=\"https:\/\/192.168.1.112\/\">https:\/\/192.168.1.112\/<\/a><\/li>\n<li>kubernetes dashboard does not work. need to run a proxy\n<pre><code class=\"language-bash\">microk8s.kubectl proxy --accept-hosts=.* --address=0.0.0.0 &<\/code><\/pre>\n<p><a href=\"http:\/\/192.168.1.112:8001\/api\/v1\/namespaces\/kube-system\/services\/https:kubernetes-dashboard:\/proxy\">http:\/\/192.168.1.112:8001\/api\/v1\/namespaces\/kube-system\/services\/https:kubernetes-dashboard:\/proxy<\/a><\/p>\n<\/li>\n<\/ul>\n<h2>next<\/h2>\n<ul>\n<li>persistent storage test<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Using Ubuntu&#8217;s MicroK8s Kubernetes environment to test a Nginx container with a NodePort and also Ingress so we can access<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[119,120],"tags":[],"class_list":["post-1657","post","type-post","status-publish","format-standard","hentry","category-kubernetes","category-microk8s"],"_links":{"self":[{"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/posts\/1657","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/comments?post=1657"}],"version-history":[{"count":0,"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/posts\/1657\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/media?parent=1657"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/categories?post=1657"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ls-al.com\/wp-json\/wp\/v2\/tags?post=1657"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}