<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jock Reed on Medium]]></title>
        <description><![CDATA[Stories by Jock Reed on Medium]]></description>
        <link>https://medium.com/@JockDaRock?source=rss-4f792e861d57------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Rgm5jhOFsiVgHCxh77zhpA.jpeg</url>
            <title>Stories by Jock Reed on Medium</title>
            <link>https://medium.com/@JockDaRock?source=rss-4f792e861d57------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:52:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@JockDaRock/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Innovation and Armed Forces in Texas]]></title>
            <link>https://medium.com/@JockDaRock/innovation-and-armed-forces-in-texas-83f2628fe9d2?source=rss-4f792e861d57------2</link>
            <guid isPermaLink="false">https://medium.com/p/83f2628fe9d2</guid>
            <category><![CDATA[military]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[sxsw-interactive]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[sxsw]]></category>
            <dc:creator><![CDATA[Jock Reed]]></dc:creator>
            <pubDate>Fri, 15 Mar 2019 14:54:56 GMT</pubDate>
            <atom:updated>2019-03-19T04:41:44.978Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rl_fNi7ojIRnMQEdc59ckQ.png" /></figure><p>SXSW Interactive has come to a close and being able to work at <a href="https://medium.com/u/2a4ca6f3d8d9">Capital Factory</a> during SXSW Interactive and seeing the buzz around the new Center for Defense Innovation has reminded me of something fun, nerdy, and also cool about Innovation in Texas and with the Armed forces.</p><p>The first microchip ever invented was by Jack Kilby, read about him here <a href="https://en.wikipedia.org/wiki/Jack_Kilby">https://en.wikipedia.org/wiki/Jack_Kilby</a>, in 1958 for Texas Instruments. In of all places Texas. I know there has always been a lot of hype about all of the technology innovations that have come out of Silicon Valley, but none of which would have been possible for what was created in Texas during a serendipitous summer at by a Missouri born engineer at Texas Instruments.</p><p>What is also interesting about the microchip is that the first Microchip was sold to the Air Force! Innovation and Armed forces in Texas seems to have had a long-standing relationship ;).</p><p>Fast forward to 2019, and <a href="https://www.afwerx.af.mil/">AFWERX</a>, <a href="https://www.army.mil/futures">Army Futures Command</a>, and Capital Factory have built an innovation center in Austin, Tx that focuses on modernizing the armed forces. And by modernization, I don’t just mean technology, I also mean the culture. In the past, a lot of what has been done with the Armed forces in technology has been closed to the public. Although some of this development and technology will obviously still remain closed. The discussions around certain technology will be in plain view of the public.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6CZ_pJJGWBIuZBHMIRuZTQ.jpeg" /><figcaption>This picture was taken during a SXSW talk on how to innovate with AFWERX.</figcaption></figure><p>A great example of this open discussion, was a couple of the talks during SXSW like “The Future of Ethical Combat with Futures Command” and “The Future of AI: Accelerating Innovation”, which were held in public view at Capital Factory. Where previously you would not have been able to have these discussions directly with military officials. Now we can.</p><p>Now, I am not saying that this will make warfare and the military a bed of roses. If we are being honest, warfare, even from a defensive posture, is always frightening, and it should be. People die in wars and battles, on both sides. I don’t know about you, but I don’t want people to die, not even my enemies. I was always taught to love my enemies and to pray for them. People that are dead cannot contribute to the human race anymore. Not in innovation, not in happiness, not anything. But I also think it would be foolish and reckless to not be prepared for our enemies. We want our military to be prepared but we also want them to be responsible. This is where I think the Center for Defense Innovation helps with that. It brings the conversation of innovation and technology for the military to a place where we the people, innovators, military personnel, and politicians can not only build cool technology but have discussions around what that technology really represents and how it should be used.</p><p>I think the real innovation here is the ability to have discussions on the responsible use of technology in an open forum. I think this helps put heart back into our military and into what we are trying to achieve as a society. A quote from one of my favorite movie / comic book characters best sums this up, “Technology is like any other power, without reason, without heart, it destroys us.” — Wonder Woman — Justice League.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*1bvmoTQimC3pWgVRoaW7Zw.jpeg" /><figcaption>From the Site MagicalQuote: <a href="https://www.magicalquote.com/wp-content/uploads/2018/03/Technology-is-like-any-other-power.-Without-reason-without-heart-it-destroys-us.jpg">https://www.magicalquote.com/wp-content/uploads/2018/03/Technology-is-like-any-other-power.-Without-reason-without-heart-it-destroys-us.jpg</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83f2628fe9d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MetalLoadBalancer: Kubernetes On-Prem /BareMetal LoadBalancing]]></title>
            <link>https://medium.com/@JockDaRock/metalloadbalancer-kubernetes-on-prem-baremetal-loadbalancing-101455c3ed48?source=rss-4f792e861d57------2</link>
            <guid isPermaLink="false">https://medium.com/p/101455c3ed48</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[k8s]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Jock Reed]]></dc:creator>
            <pubDate>Tue, 18 Sep 2018 21:27:16 GMT</pubDate>
            <atom:updated>2018-09-18T21:43:25.339Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>If you are looking to ramp up on Kubernetes before diving into load balancing, please check out some of these guides, articles and tutorials to get you started… <a href="https://www.lynda.com/Kubernetes-tutorials/Kubernetes-Microservices/691061-2.html">https://www.lynda.com/Kubernetes-tutorials/Kubernetes-Microservices/691061-2.html</a>, <a href="https://github.com/kelseyhightower/kubernetes-the-hard-way">https://github.com/kelseyhightower/kubernetes-the-hard-way</a>, <a href="https://medium.com/@JockDaRock/minikube-on-windows-10-with-hyper-v-6ef0f4dc158c">https://medium.com/@JockDaRock/minikube-on-windows-10-with-hyper-v-6ef0f4dc158c</a></blockquote><p>If you have ever deployed applications to Kubernetes (k8s) on Google Cloud, AWS, or Azure, you notice how quickly you can deploy your app and have it reachable, externally (public IP), from the k8s cluster within a matter of a couple minutes. You merely have to set the service type of your application to LoadBalancer on your service manifest and k8s contacts an Elastic / Cloud Load Balancer and procures an IP address for your app.</p><p>Now, if you are looking to see the same functionality for your on-prem k8s clusters, you are typically disappointed. K8s uses glue code to automagically work with Cloud Providers’ LoadBalancers. This means if you assign a LoadBalancer type to your services for bare metal or on-prem deployments, you will literally be waiting forever for your external IP address.</p><p>The options for the service types you end up with for on-prem k8s deployments are NodePort or externalIPs. You can read more about service types here <a href="https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types">https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types</a>.</p><p>NodePort is workable, but you are confined to using the IP address of your k8s nodes, and defaults to ports 30000–32767 for access to outside of the k8s cluster. You can use externalIPs but the IP address already has to be pre-configured to route directly to one of your cluster nodes.</p><p>Both NodePort and externalIP addresses are limiting in different ways and are really not an ideal solution for on-prem or internal k8s deployments. Not to mention, if you would like to test applications with LoadBalancing without having to use up expensive IP addresses on your cloud provider, you are kind of stuck.</p><p><strong>Enter Metal LB</strong></p><p>Metal LB (<a href="https://metallb.universe.tf/">https://metallb.universe.tf/</a>, <a href="https://github.com/google/metallb">https://github.com/google/metallb</a>) is a load balancer for your bare metal / on-prem deployments. It uses standard networking appliances (real or virtual) to distribute IP addresses that are external to your cluster and assigns those IP addresses to your app services that specify the LoadBalancer type. The implementation is easy to apply on your k8s cluster and you could be up and running within 5 minutes.</p><p>Ok, great, thanks for telling me about this, but how do I use it? Good question, I have a put together a couple of tutorials to get you started depending on your setup of Kubernetes.</p><p>For your Dev Environment on DockerCE: <a href="https://medium.com/@JockDaRock/kubernetes-metal-lb-for-docker-for-mac-windows-in-10-minutes-23e22f54d1c8">https://medium.com/@JockDaRock/kubernetes-metal-lb-for-docker-for-mac-windows-in-10-minutes-23e22f54d1c8</a></p><p>For On-Prem Kubernetes Deployment:</p><p><a href="https://medium.com/@JockDaRock/kubernetes-metal-lb-for-on-prem-baremetal-cluster-in-10-minutes-c2eaeb3fe813">https://medium.com/@JockDaRock/kubernetes-metal-lb-for-on-prem-baremetal-cluster-in-10-minutes-c2eaeb3fe813</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=101455c3ed48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes Metal LB for Docker for Mac/Windows in 10 Minutes]]></title>
            <link>https://medium.com/@JockDaRock/kubernetes-metal-lb-for-docker-for-mac-windows-in-10-minutes-23e22f54d1c8?source=rss-4f792e861d57------2</link>
            <guid isPermaLink="false">https://medium.com/p/23e22f54d1c8</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[k8s]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Jock Reed]]></dc:creator>
            <pubDate>Tue, 18 Sep 2018 21:27:10 GMT</pubDate>
            <atom:updated>2018-09-18T21:27:10.307Z</atom:updated>
            <content:encoded><![CDATA[<p>In this quickstart with Metal LB we will quickly get an on-prem / bare metal load balancer running on Kubernetes (k8s) with the Docker CE edition for Windows or Mac version of Kubernetes. This will give us a good dev environment for testing.</p><p><strong>Pre-Reqs:</strong></p><ol><li>Docker CE for Mac / Windows installed (<a href="https://docs.docker.com/v17.12/docker-for-mac/install/">https://docs.docker.com/v17.12/docker-for-mac/install/</a> , <a href="https://docs.docker.com/v17.12/docker-for-windows/install/">https://docs.docker.com/v17.12/docker-for-windows/install/</a>)</li><li>Kubernetes-cli program or kubectl. For mac you should be able to get this with the homebrew package manager and the command line command brew install kubernetes-cli. Or if you are on Windows and have the chocolatey package manager you can use choco install kubernetes-cli. You can also use this guide as well <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl/">https://kubernetes.io/docs/tasks/tools/install-kubectl/</a>.</li><li>Kubernetes enabled on your Docker CE for your desktop. (<a href="https://docs.docker.com/docker-for-mac/#kubernetes">https://docs.docker.com/docker-for-mac/#kubernetes</a>, <a href="https://docs.docker.com/docker-for-windows/#kubernetes">https://docs.docker.com/docker-for-windows/#kubernetes</a>). Follow the instructions completely for enabling k8s, as this will also help to configure your kubectl program as well.</li></ol><p><strong>Optional:</strong></p><p>Check out the docs and github repo for MetalLB for more in depth study <a href="https://metallb.universe.tf/">https://metallb.universe.tf/</a>, <a href="https://github.com/google/metallb">https://github.com/google/metallb</a>.</p><p>Now that we have the pre-reqs out of the way let’s get started.</p><p>First we need to apply the MetalLB manifest.</p><p>kubectl apply -f <a href="https://raw.githubusercontent.com/google/metallb/v0.7.3/manifests/metallb.yaml">https://raw.githubusercontent.com/google/metallb/v0.7.3/manifests/metallb.yaml</a></p><p>Next we want to check that the controller and the speaker are running. we can do this by using this command.</p><p>kubectl get pods -n metallb-system</p><p>Once those pods are running we can deploy our MetalLB configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/509/1*Ux8azXE9M_mU8zisaSbjGw.png" /></figure><p>Next we want to deploy a configuration that will work with Docker CE. Typically we would deploy the MetalLB to communicate with a router with dhcp enabled or BGP router. But for purposes of the Docker CE enviroment for Mac and Windows we will deploy it to work with the localhost environment of our Desktop. This will help us if we are wanting to test MetalLB behind a corporate firewall and don’t have access to BGP routing or ARP routing policies. For more on check out the docs on the MetalLB site <a href="https://metallb.universe.tf/concepts/">https://metallb.universe.tf/concepts/</a>. For this quickstart we will be using the layer 2 configuration as it is the easiest to get started with.</p><p>So next we will look at our configuration.</p><pre>apiVersion: v1<br>kind: ConfigMap<br>metadata:<br>  namespace: metallb-system<br>  name: config<br>data:<br>  config: |<br>    address-pools:<br>    - name: my-ip-space<br>      protocol: layer2<br>      addresses:<br>      - 127.0.0.240/28</pre><p>You will notice the addresses will only be local to our Desktop. The reason for this, is due to DockerCE being NATed as a virtual machine on Mac and Windows. Even if you had everything properly configure on your network for using layer 2 and DHCP, your work or home router would not even know how to reach DockerCE as it is being NATed which makes any services only available on the localhost. In a more standard deployment your addresses would look more like this 10.0.1.240/28 or something similar.</p><p>That being said, you can access this exact configuration here <a href="https://raw.githubusercontent.com/JockDaRock/metallb-testing/master/layer2-dockerce.yml">https://raw.githubusercontent.com/JockDaRock/metallb-testing/master/layer2-dockerce.yml</a> and download and modify if you need to. If not we can apply this configuration as is.</p><p>kubectl apply -f <a href="https://raw.githubusercontent.com/JockDaRock/metallb-testing/master/layer2-dockerce.yml">https://raw.githubusercontent.com/JockDaRock/metallb-testing/master/layer2-dockerce.yml</a></p><p>Once we have deployed our configuration we are ready to apply our deployment and service manifest.</p><blockquote>Note: Since these k8s deployments are using your localhost IP address scheme for your applications, please be sure to note the port you are applying to to make sure you are not trying to map to a port where are service is currently being used.</blockquote><pre>apiVersion: apps/v1beta2<br>kind: Deployment<br>metadata:<br>  name: nginx<br>spec:<br>  selector:<br>    matchLabels:<br>      app: nginx<br>  template:<br>    metadata:<br>      labels:<br>        app: nginx<br>    spec:<br>      containers:<br>      - name: nginx<br>        image: nginx:1<br>        ports:<br>        - name: http<br>          containerPort: 80<br><br>---<br>apiVersion: v1<br>kind: Service<br>metadata:<br>  name: nginx<br>spec:<br>  ports:<br>  - name: http<br>    port: 8080<br>    protocol: TCP<br>    targetPort: 80<br>  selector:<br>    app: nginx<br>  type: LoadBalancer</pre><p>The above configuration is what we are using to deploy our first application. I changed this slightly from the tutorial on the main docs site. This will deploy an nginx app/service to kubernetes that we will be able to access. You can download and change this file as needed (<a href="https://raw.githubusercontent.com/JockDaRock/metallb-testing/master/nginxlb.yml">https://raw.githubusercontent.com/JockDaRock/metallb-testing/master/nginxlb.yml</a>) or use as is.</p><p>Use the following command kubectl apply -f <a href="https://raw.githubusercontent.com/JockDaRock/metallb-testing/master/nginxlb.yml">https://raw.githubusercontent.com/JockDaRock/metallb-testing/master/nginxlb.yml</a></p><p>We can verify the IP address is assigned by using the kubectl get services command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*MTV4mPyXRgGpeOGzX3G6yw.png" /></figure><p>Once the service is up and running we can go to it on a browser of our choice at <a href="http://127.0.0.1:8080.">http://127.0.0.1:8080.</a></p><p>Even though your address will come back as 127.0.0.240, it will all be accessible through your local host address. On Mac this will only be routable by visiting either 127.0.0.1:8080 or localhost:8080. On Windows you should be able to access Nginx on 127.0.0.240:8080 as well as 127.0.0.1:8080.</p><p>You are now ready to go forth to use your new LoadBalancing skills. Let me know how your experience</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23e22f54d1c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes Metal LB for On-Prem / BareMetal Cluster in 10 minutes]]></title>
            <link>https://medium.com/@JockDaRock/kubernetes-metal-lb-for-on-prem-baremetal-cluster-in-10-minutes-c2eaeb3fe813?source=rss-4f792e861d57------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2eaeb3fe813</guid>
            <category><![CDATA[k8s]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Jock Reed]]></dc:creator>
            <pubDate>Tue, 18 Sep 2018 21:27:04 GMT</pubDate>
            <atom:updated>2018-10-30T20:05:46.621Z</atom:updated>
            <content:encoded><![CDATA[<p>In this quickstart with Metal LB we will quickly get an on-prem / bare metal load balancer running on Kubernetes (k8s). This is more of a standard layer 2 MetalLB environment. If you would prefer more of a developer related environment on Docker CE, please refer to this guide <a href="https://medium.com/@JockDaRock/kubernetes-metal-lb-for-docker-for-mac-windows-in-10-minutes-23e22f54d1c8">https://medium.com/@JockDaRock/kubernetes-metal-lb-for-docker-for-mac-windows-in-10-minutes-23e22f54d1c8</a>.</p><p><strong>Pre-Reqs:</strong></p><ol><li>K8s Cluster with no other load balancers installed. Check out <a href="https://medium.com/u/89b4ba5a32ff">Alex Ellis</a> guides for getting up and running with bare metal kubernetes here if you need help getting started (<a href="https://blog.alexellis.io/kubernetes-in-10-minutes/">https://blog.alexellis.io/kubernetes-in-10-minutes/</a>, <a href="https://blog.alexellis.io/serverless-kubernetes-on-raspberry-pi/">https://blog.alexellis.io/serverless-kubernetes-on-raspberry-pi/</a>).</li><li>Kubernetes-cli program or kubectl. For mac you should be able to get this with the homebrew package manager and the command line command brew install kubernetes-cli. Or if you are on Windows and have the chocolatey package manager you can use choco install kubernetes-cli. You can also use this guide as well <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl/">https://kubernetes.io/docs/tasks/tools/install-kubectl/</a>.</li><li>Your default gateway router configured for DHCP and able to hand out IP addresses.</li></ol><p><strong>Optional:</strong></p><p>Check out the docs and github repo for MetalLB for more in depth study <a href="https://metallb.universe.tf/">https://metallb.universe.tf/</a>, <a href="https://github.com/google/metallb">https://github.com/google/metallb</a>.</p><p><strong>The environment I am Using:</strong></p><blockquote>Your environment might be a little bit or vastly different than this, but should still work given the above pre-reqs.</blockquote><ul><li>Host: Ubuntu 18.04 Server 16 GB RAM, 4 CPUs running on VirtualBox on a Windows 10 Computer.</li><li>Kube Cluster: Single Node Cluster Version, Kubernetes Version 1.11.3</li><li>Network: VLANed network running on <a href="https://create.meraki.io/">Meraki</a> with DHCP configured for 192.168.X.X network.</li></ul><p>Now that we have the pre-reqs out of the way let’s get started.</p><p>First we need to apply the MetalLB manifest.</p><p>kubectl apply -f <a href="https://raw.githubusercontent.com/google/metallb/v0.7.3/manifests/metallb.yaml">https://raw.githubusercontent.com/google/metallb/v0.7.3/manifests/metallb.yaml</a></p><p>Next we want to check that the controller and the speaker are running. we can do this by using this command.</p><p>kubectl get pods -n metallb-system</p><p>Once those pods are running we can deploy our MetalLB configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/1*zeatr2qRuGikHHKdwbfRiw.png" /></figure><p>So next we will look at our configuration.</p><pre>apiVersion: v1<br>kind: ConfigMap<br>metadata:<br>  namespace: metallb-system<br>  name: config<br>data:<br>  config: |<br>    address-pools:<br>    - name: my-ip-space<br>      protocol: layer2<br>      addresses:<br>      - 192.168.1.240/28</pre><p>You will notice the addresses are using a 192.168.X.X network. Please modify this to match the IP scheme of the network you are connected to. You can change this to something like10.0.1.240/28 or something similar.</p><p>That being said, you can access this exact configuration here <a href="https://raw.githubusercontent.com/google/metallb/v0.7.3/manifests/example-layer2-config.yaml">https://raw.githubusercontent.com/google/metallb/v0.7.3/manifests/example-layer2-config.yaml</a> and download and modify if you need to. If not, we can apply this configuration as is.</p><p>kubectl apply -f <a href="https://raw.githubusercontent.com/google/metallb/v0.7.3/manifests/example-layer2-config.yaml">https://raw.githubusercontent.com/google/metallb/v0.7.3/manifests/example-layer2-config.yaml</a></p><p>Once we have deployed our configuration we are ready to apply our deployment and service manifest.</p><pre>apiVersion: apps/v1beta2<br>kind: Deployment<br>metadata:<br>  name: nginx<br>spec:<br>  selector:<br>    matchLabels:<br>      app: nginx<br>  template:<br>    metadata:<br>      labels:<br>        app: nginx<br>    spec:<br>      containers:<br>      - name: nginx<br>        image: nginx:1<br>        ports:<br>        - name: http<br>          containerPort: 80</pre><pre>---<br>apiVersion: v1<br>kind: Service<br>metadata:<br>  name: nginx<br>spec:<br>  ports:<br>  - name: http<br>    port: 8080<br>    protocol: TCP<br>    targetPort: 80<br>  selector:<br>    app: nginx<br>  type: LoadBalancer</pre><p>The above configuration is what we are using to deploy our first application. I changed this slightly from the tutorial on the main docs site. This will deploy an nginx app/service to kubernetes that we will be able to access. You can download and change this file as needed (<a href="https://raw.githubusercontent.com/JockDaRock/metallb-testing/master/nginxlb.yml">https://raw.githubusercontent.com/JockDaRock/metallb-testing/master/nginxlb.yml</a>) or use as is.</p><p>Use the following command kubectl apply -f <a href="https://raw.githubusercontent.com/JockDaRock/metallb-testing/master/nginxlb.yml">https://raw.githubusercontent.com/JockDaRock/metallb-testing/master/nginxlb.yml</a></p><p>We can verify the IP address is assigned by using the kubectl get services command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*-qSTOk04llO5tBnypltefg.png" /></figure><p>Once the service is up and running we can access it on a browser of our choice at the External IP address listed on port 8080.</p><p>You are now ready to go forth to use your new LoadBalancing skills. Let me know how your experience is and if you have any questions.</p><p>Check out some other guides and tutorials if you are looking to get started with Kubernetes:</p><p><a href="https://medium.com/@JockDaRock/minikube-on-windows-10-with-hyper-v-6ef0f4dc158c">Minikube on Windows 10 with Hyper-V</a></p><p><a href="https://www.lynda.com/Kubernetes-tutorials/Kubernetes-Microservices/691061-2.html">https://www.lynda.com/Kubernetes-tutorials/Kubernetes-Microservices/691061-2.html</a></p><p><a href="https://github.com/kelseyhightower/kubernetes-the-hard-way">GitHub - kelseyhightower/kubernetes-the-hard-way: Bootstrap Kubernetes the hard way. No scripts.</a></p><p>Also, check the standard guide from the MetalLB site out. I started with this guide while I was learning about MetalLB <a href="https://metallb.universe.tf/tutorial/layer2/">https://metallb.universe.tf/tutorial/layer2/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2eaeb3fe813" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OpenFaaS on Minikube: Serverless on Kubernetes for Windows 10]]></title>
            <link>https://medium.com/@JockDaRock/openfaas-on-minikube-serverless-on-kubernetes-for-windows-10-3c7c7d68f47f?source=rss-4f792e861d57------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c7c7d68f47f</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[csharp]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[windows-10]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Jock Reed]]></dc:creator>
            <pubDate>Sat, 13 Jan 2018 10:06:30 GMT</pubDate>
            <atom:updated>2018-01-13T10:09:47.698Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog post will guide you through installing and getting started with OpenFaaS and Kubernetes through the use of Minikube on Windows 10.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/1*vMEcwH5CYFXdaX-TTkfgKw.png" /><figcaption>Copyright © OpenFaaS Ltd</figcaption></figure><p>If you are also using minikube on Mac, then please checkout this guide from the author of OpenFaaS, <a href="https://medium.com/u/89b4ba5a32ff">Alex Ellis</a>, on installing OpenFaaS on minikube for Mac.</p><p><a href="https://medium.com/devopslinks/getting-started-with-openfaas-on-minikube-634502c7acdf">https://medium.com/devopslinks/getting-started-with-openfaas-on-minikube-634502c7acdf</a></p><h3><strong>Contents</strong></h3><ol><li>Minikube, Docker and Other Dependencies</li><li>Install the OpenFaaS CLI program: faas-cli</li><li>Install OpenFaaS</li><li>Deploy Your First Function from the OpenFaaS Function Store</li><li>Build and Deploy a CSharp function using the OpenFaaS CLI</li></ol><h3>Minikube, Docker and Other Dependencies</h3><ol><li><a href="https://chocolatey.org/"><strong>Chocolatey package manager</strong></a> for Windows: Please use this guide from my blog post here if you need help getting started (<a href="https://medium.com/@JockDaRock/installing-the-chocolatey-package-manager-for-windows-3b1bdd0dbb49">https://medium.com/@JockDaRock/installing-the-chocolatey-package-manager-for-windows-3b1bdd0dbb49</a>).</li><li><strong>Minikube</strong>:<strong> </strong>You will need to have minikube installed on Windows before starting with OpenFaaS. Please also use the following guide I compiled for using Minikube on HyperV for Windows 10 (<a href="https://medium.com/@JockDaRock/minikube-on-windows-10-with-hyper-v-6ef0f4dc158c">https://medium.com/@JockDaRock/minikube-on-windows-10-with-hyper-v-6ef0f4dc158c</a>).</li><li><strong>Docker</strong>: You can use the Chocolatey package to install this one, <strong>choco install docker</strong>. You will need this in combination with the OpenFaaS cli program to build the Docker images that hold the functions.</li><li><strong>Helm</strong>: Once you have the Chocolatey Package manager and Minikube installed on your Windows 10 computer, we will need to install Helm which is a package manager for Kubernetes. We will use Helm to install OpenFaaS to our Kubernetes Cluster on Minikube. Use this guide to install Helm (<a href="https://medium.com/@JockDaRock/take-the-helm-with-kubernetes-on-windows-c2cd4373104b">https://medium.com/@JockDaRock/take-the-helm-with-kubernetes-on-windows-c2cd4373104b</a>)</li><li><strong>Git</strong>: Install git on Windows. We will use git to copy the code repos we need for OpenFaaS. In an Admin Windows command line, type <strong>choco install git</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*ful0fvu84-i4BnIAs2xIQw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/1*n7IM-YIKBtRew17xTFQPYA.png" /></figure><p>6. Signup for a Docker Hub account (if you do not already have a Docker Hub account). We will need a place to push the Docker image of our function, for the <strong>Build and Deploy a CSharp function using the OpenFaaS CLI </strong>portion of this guide. You can sign up here (h<a href="https://hub.docker.com/">ttps://hub.docker.com/</a>). It is free and easy to signup.</p><p>Once you have completed those steps, you are ready to install OpenFaaS.</p><blockquote><strong>Optional, but Recommended Packages</strong>: In the last section of this tutorial I will be using a few programs that are not installed with Windows. You can use native Windows packages to accomplish those tasks if you are more familiar with those programs. That being said all of the packages I will be using can also be installed using chocolatey and the following commands: <strong>choco install curl</strong>, <strong>choco install notepadplusplus</strong>, <strong>choco install postman</strong>.</blockquote><h3>Install the OpenFaaS CLI program: faas-cli</h3><p>Open an Admin command line window and use chocolatey to install the OpenFaaS CLI program.</p><pre>choco install faas-cli</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BS83GtzkC861_SKxqjzvDA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eW5fT9GgJfGYHl0Xod7Fbg.png" /></figure><h3>Install OpenFaaS</h3><p>To install OpenFaas we need to clone the git repo for <a href="https://github.com/openfaas/faas-netes">faas-netes</a>, which is the Kubernetes implementation of OpenFaaS. Navigate to a directory of your choice on the Windows command line and then clone the repo.</p><pre>git clone https://github.com/openfaas/faas-netes</pre><p>Change the directory to where faas-netes was downloaded.</p><pre>cd faas-netes</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/994/1*FEc9p41p_Y25lYG2yFE5Og.png" /></figure><p>Assuming you installed Helm from the packages section, use the following Helm command to install OpenFaaS to your Kubernetes Cluster on Minikube.</p><blockquote>Note: If you have not initialized Helm for your Minikube cluster when you installed it to Windows, you can do so now by typing <strong>helm init </strong>in the command line window.</blockquote><pre>helm upgrade --install --debug --reset-values --set async=false --set rbac=false openfaas openfaas</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zg5KcqqEZJOjH4VxfZuM0g.png" /></figure><p>Let’s check to make sure OpenFaaS is running by looking to see if the Web UI is up.</p><p>First we need to find the IP address. Type minikube ip in your command line window.</p><pre>minikube ip</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*63fVpQnJxiJUBhz4xzlwAg.png" /></figure><p>Using that IP address navigate to your IP address of your minikube on port <strong>31112</strong>.</p><pre>http://&lt;minikube_ip&gt;:31112/ui/</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OpR2Z_wDU9PcR0N-n2pPYw.png" /></figure><p>You now have OpenFaaS installed! Time for the fun.</p><h3>Deploy Your First Function from the OpenFaaS Function Store</h3><p>We are going to deploy our first function with OpenFaaS using the Web UI and the Function Store.</p><p>In a web browser navigate to the same URL we used to get to the Web UI.</p><pre>http://&lt;minikube_ip&gt;:31112/ui/</pre><p>Click on the <strong>Deploy New Function</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*BIPJ-9c6GEhFF0oc97W1Pw.png" /></figure><p>Select the <strong>nslookup</strong> function and then click <strong>Deploy.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ixtUNvGP0n3Cw-W3vjnkpA.png" /></figure><p>In the <strong>Request Body </strong>type in a domain name, to test the nslookup function, e.g developer.cisco.com, and then click the <strong>Invoke </strong>button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PQy6eT0IxHcT18AgkFgdyw.png" /></figure><p>If you prefer to call the function in a more programmatic way and you have one of the Optional, but Recommended packages installed for this tutorial. From the command line you can use the <strong>curl </strong>command to call the function.</p><pre>curl -X POST <a href="http://172.16.0.127:31112/function/nslookup">http://&lt;minikube_ip&gt;:31112/function/nslookup</a> -d &#39;developer.cisco.com&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XRqb6xpthgCvoF_zASmzfQ.png" /></figure><p>Or Postman…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FluC55BoTSj0E2j3qv4jSA.png" /></figure><p>Congrats on deploying your first function!</p><h3>Build and Deploy a CSharp function using the OpenFaaS CLI program</h3><p>Using the Windows command line. In a directory of your choosing create an additional directory named <strong>functions</strong> and then change to that directory on the command line.</p><pre>mkdir functions &amp;&amp; cd functions</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*NLPaql8N7CdidwuuIabdTQ.png" /></figure><p>Using the OpenFaaS CLI program pull down the code templates we will use to build and deploy our function.</p><pre>faas-cli template pull</pre><p>Create a new function with faas-cli and the C# language.</p><pre>faas-cli new win-func --lang csharp</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/995/1*Kv0_2VLRyYvdrkoJQ6Wa0Q.png" /></figure><p>This will have created a file folder called <strong>win-func</strong> and a <strong>win-func.yml</strong> file.</p><p>In the <strong>win-func</strong> folder their is a file called <strong>FunctionHandler.cs</strong>. I will be editing this file with the NotePad++ program. However you can use the native Windows Notepad editor if you want to edit the csharp file that way.</p><p>Open the <strong>FunctionHandler.cs</strong> handler in your text / code editor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uBZiB3iLIkraAx4mRGLmtw.png" /></figure><p>On line 9, at the end of <strong>Console.WriteLine, </strong>add the following text…</p><pre>+ &quot;. Welcome to TEAM SERVERLESS&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*byAVqOqjkLzN5DyCxt_y_g.png" /></figure><p>Save the file.</p><p>Using the same editor to open the win-func.yml file.</p><p>Edit the gateway to reflect the OpenFaaS gateway.</p><pre>gateway: <a href="http://172.16.0.127:31112/">http://172.16.0.127:31112</a></pre><p>Then edit the image portion to reflect your Docker Hub username and the name of your function.</p><pre>image: &lt;docker_hub_username&gt;/win-func</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/755/1*WjTtfxIr4i7ma4t4M4YODw.png" /></figure><p>Save the win-func.yml file.</p><p>In a command line window, build the function with the faas-cli.</p><pre>faas-cli build -f win-func.yml</pre><p>If you have not already done so, login to your docker hub account from the CLI.</p><pre>docker login</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*0ivvjgpt6dvwArayXaQDRg.png" /></figure><p>Now push the function image to docker hub.</p><pre>faas-cli push -f win-func.yml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qwcnUfUdNv3MB5HvURnTdw.png" /></figure><p>Deploy the function to the Kubernetes cluster.</p><pre>faas-cli deploy -f win-func.yml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*gcU79Ygw6KRsE4-WcOA8FQ.png" /></figure><p>Now we will test the function. On the OpenFaas Web UI, write a message in the Request Body and then Invoke the function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pyFsERusA2olo7UHipLn1A.png" /></figure><p>Or you can use the curl function we used previously to invoke the <strong>win-func</strong> function from the Windows command line.</p><pre>curl -X POST <a href="http://172.16.0.127:31112/function/win-func">http://&lt;minikube_ip&gt;:31112/function/win-func</a> -d &quot;OpenFaaS Rocks!&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JQAPW4MgL60fe6B-EzGaQQ.png" /></figure><p>You are now a Serverless ninja!</p><h3>Last Words</h3><p>Visit the GitHub repo (<a href="https://github.com/openfaas/faas">https://github.com/openfaas/faas</a>), <strong>star</strong> the project, and join the community.</p><p>You can also suggest and submit functions to the function store (<a href="https://github.com/openfaas/store">https://github.com/openfaas/store</a>). Check out this blog to learn about my first submission to the function store.</p><p><a href="https://hackernoon.com/merged-my-first-submission-to-the-openfaas-function-store-4a35b5cd366c">Merged! My first submission to the OpenFaaS Function Store</a></p><p>Checkout this guide for using Kubernetes in an environment that is closer to what you might see in production.</p><p><a href="https://blog.devnetcreate.io/serverless-at-the-helm-in-kubernetes-in-the-devnet-sandbox-2038031a3f4b">OpenFaaS At The Helm w/ Kubernetes in the DevNet Sandbox</a></p><p>If you are interested in learning more about what serverless is from an architectural standpoint and how OpenFaaS fits in that picture, then please watch this YouTube video from <a href="https://medium.com/u/89b4ba5a32ff">Alex Ellis</a> from KubeCon on OpenFaaS.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FXgsxqHQvMnM%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DXgsxqHQvMnM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FXgsxqHQvMnM%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bf0ab6def720af479f06f16c67164c45/href">https://medium.com/media/bf0ab6def720af479f06f16c67164c45/href</a></iframe><p>Follow <a href="https://twitter.com/openfaas">OpenFaaS on Twitter</a> for all the latest Cool Hacks, demos and news, Or follow <a href="https://twitter.com/JockDaRock">me on Twitter, JockDaRock</a>, for cool tech like this on a regular basis.</p><p>Also check out more of my blogs on medium by visiting <a href="https://medium.com/@JockDaRock">https://medium.com/@JockDaRock</a>. Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c7c7d68f47f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Serverless at the Edge: Up and Running w/ OpenFaaS & Docker on a Raspberry Pi Multi-Node Cluster…]]></title>
            <link>https://medium.com/@JockDaRock/serverless-at-the-edge-up-and-running-w-openfaas-docker-on-a-raspberry-pi-multi-node-cluster-e0957f4d8a49?source=rss-4f792e861d57------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0957f4d8a49</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Jock Reed]]></dc:creator>
            <pubDate>Fri, 12 Jan 2018 19:05:07 GMT</pubDate>
            <atom:updated>2018-01-12T19:05:07.444Z</atom:updated>
            <content:encoded><![CDATA[<h3>Serverless at the Edge: Up and Running w/ OpenFaaS &amp; Docker on a Raspberry Pi Multi-Node Cluster with PiBakery</h3><p>This guide will focus on getting you up and running with Serverless Functions as a Service (FaaS) and a Raspberry Pi (RPi) cluster as quickly as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/1*n72rwlzdN-gTcNwuli4ibQ.png" /></figure><p>If you want a guide that gives you a bit more experience with the RPi command line and gives you an overview of Serverless as an architectural design, then please visit <a href="https://medium.com/u/89b4ba5a32ff">Alex Ellis</a>’s guide (<a href="https://blog.alexellis.io/your-serverless-raspberry-pi-cluster/">https://blog.alexellis.io/your-serverless-raspberry-pi-cluster/</a>). My guide focuses on automating the RPi provisioning through PiBakery get you up and running a little quicker.</p><p>Also if you want to learn more about OpenFaaS and Serverless please checkout Alex Ellis’ talk from KubeCon this last December.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FXgsxqHQvMnM%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DXgsxqHQvMnM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FXgsxqHQvMnM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d36069542f691b83bce75109abac7ac2/href">https://medium.com/media/d36069542f691b83bce75109abac7ac2/href</a></iframe><h3><strong>Contents</strong></h3><ol><li>Pre-Requisites for Mac and Windows</li><li>Flashing your micro SD cards with PiBakery and Deploying Docker Swarm</li><li>Install OpenFaaS</li><li>Deploy your first function with the Function Store</li><li>Deploy a function with the OpenFaaS CLI program.</li></ol><h3><strong>Pre-Requisites for Mac and Windows</strong></h3><p>You will need a few things on your laptop before getting started.</p><ul><li>At Least 2 Raspberry Pi development boards.</li><li>Power supplies for RPis, ethernet cables (if using wired internet access), and micro SD cards for the file system for RPis.</li><li><strong>PiBakery on your laptop</strong>. If you are on Mac you can use this guide <a href="http://www.pibakery.org/docs/install-mac.html">http://www.pibakery.org/docs/install-mac.html</a> to install. If you are on Windows and you have the Chocolately package manager installed, use the <strong>choco install pibakery</strong> command from the command line. Or you can use this guide <a href="http://www.pibakery.org/docs/install-win.html">http://www.pibakery.org/docs/install-win.html</a> for Windows setup.</li><li><strong>Git</strong> installed on your laptop. If you have the Homebrew package manager installed on Mac or Chocolatey installed for Windows on your laptop can use the command <strong>brew install git</strong> or <strong>choco install git</strong>. Or you can follow this guide to install git on the operating system of your choice <a href="https://git-scm.com/book/en/v2/Getting-Started-Installing-Git">https://git-scm.com/book/en/v2/Getting-Started-Installing-Git</a>.</li><li><strong>Windows Only</strong>: make sure you have a program like <strong>Putty </strong>or if you are on Windows 10, make sure you have the Linux Subsystem app installed so you can SSH into the Raspberry Pi master. You can use the command <strong>choco install putty</strong> to install or use this guide <a href="https://www.ssh.com/ssh/putty/windows/install">https://www.ssh.com/ssh/putty/windows/install</a>. Use the following guides if you want to install the Linux Subsystem app on Windows 10…<a href="https://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/">https://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/</a> and <a href="https://docs.microsoft.com/en-us/windows/wsl/install-win10">https://docs.microsoft.com/en-us/windows/wsl/install-win10</a></li></ul><h3><strong>Flashing your micro SD cards with PiBakery and Deploying Docker Swarm</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zxYZ-w4utZoCKvmYTjwwGQ.png" /></figure><p>Open up a command line window and clone the repository with the PiBakery recipes we will need.</p><pre>git clone <a href="https://github.com/JockDaRock/openfaas_pibakery_config">https://github.com/JockDaRock/openfaas_pibakery_config</a></pre><p>Make note of where this directory is being stored on your computer (e.g. /&lt;location&gt;/&lt;of git&gt;/&lt;repo&gt;/openfaas_pibakery_config or c:\&lt;location&gt;\&lt;of git&gt;\&lt;repo&gt;\openfaas_pibakery_config)</p><p>Open up your PiBakery program. You will be required to open it up with elevated permissions, in both Windows and Mac. Click the Import button.</p><p>Navigate to the file folder where you cloned the <strong>openfaas_pibakery_config</strong> directory and open the <strong>multi_node_swarm </strong>folder. Select the <strong>OpenFaaS_master.xml</strong> file and open it. Below is what the imported file should look like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*FTSL773LnAhA6Z9Qvt7eaQ.png" /></figure><blockquote><em>This configuration requires you to have internet connectivity as soon as it is booted to install all of the packages on first boot. You can edit this configuration to have WiFi credentials if you wish to not use a wired connection. However, I have not always had the best of luck with RPi clusters over WiFi. So I typically choose to leave the configuration as is and use a wired connection.</em></blockquote><p>Insert your micro SD card into your laptop computer. Click this Write button on PiBakery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/1*BsmQKo-zyXjpNVAY0etE0A.png" /></figure><p>Select the appropriate SD card if you have more than one connected to your computer. Then select <strong>Raspbian Lite</strong> for the <strong>Operating System</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/242/1*SsH4DxYnymRS5oDz2ExvhQ.png" /></figure><p>Click Write. This process will take a few minutes to complete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/241/1*bG200mVAqDfn9c8NdMZuHg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/242/1*p80o82wU1B29LqAi-4Oa4g.png" /></figure><p>Remove the SD card from your computer and and insert it into your first RPi. This will end up being your Master node for swarm.</p><p>Plug your ethernet cable into your RPi and a network switch/router.</p><p>Plug the power cable into the RPi. This is will take a few minutes to complete. After the RPi reboots, we will SSH tunnel into the RPi to check.</p><p>SSH into the RPi using the hostname set by PiBakery.</p><pre>ssh pi@master-openfaas.local</pre><p>Password is <strong>raspberry</strong>.</p><p>Once you are logged in we can check to make sure docker swarm was setup properly by typing…</p><pre>sudo docker node ls</pre><p>Once docker swarm is running it should list our first node as leader.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*eyd4rIFwePxiykLWKYPzog.png" /></figure><p>After we have verified docker swarm is running on our master node, we need to get the <strong>join-token </strong>for the worker nodes to be connected to our swarm cluster. While still being SSHed into the RPi, type the following command in the terminal window…</p><pre>sudo docker swarm join-token worker</pre><p>Your token should look similar to this…</p><pre>docker swarm join --token SWMTKN-1-0uz05xzumtazh0rmlkro2pxy8e6882jd9wkmm49w4ptcc0ucr8-3pna808fpoawa0axnu4t5a7aa 172.16.99.13:2377</pre><p>We will use this token to setup our worker node with PiBakery.</p><p>In PiBakery click the import button and in the same directory we imported the OpenFaaS_master.xml file, we will import the <strong>OpenFaaS_worker.xml</strong> file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*DwTsAadIC1ytwUSENHSgtw.png" /></figure><p>Using the join-token command we retrieved from the master node, we will paste that command with <strong>sudo </strong>in the last run command in PiBakery.</p><blockquote>Note: Please make sure the <strong>sudo </strong>command is inserted in the last command, otherwise PiBakery will not be able to auto join the docker swarm cluster.</blockquote><pre>sudo docker swarm join --token SWMTKN-1-0uz05xzumtazh0rmlkro2pxy8e6882jd9wkmm49w4ptcc0ucr8-3pna808fpoawa0axnu4t5a7aa 172.16.99.13:2377</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*ZZBFHFbxYKFBF_tVWp-rsg.png" /></figure><p>Click the <strong>Write</strong> button again and once the process is complete eject the SD card, insert the SD card into your second RPi, connect the ethernet cable, and last the power cable. Repeat this step as many time as you need for however many worker nodes you will include in your cluster.</p><p>It will take a few minutes for your worker(s) to join the swarm. While still being SSHed into the master RPi, you can use the same node command as before to check for when each worker node joins the cluster.</p><pre>sudo docker node ls</pre><p>Once your node(s) have joined the cluster, you are ready to install OpenFaaS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*fc5mnz2rB0niFykpoIoblw.png" /></figure><h3><strong>Install OpenFaaS</strong></h3><p>Using the SSH terminal window for the master RPi, change your current current directory to <strong>faas</strong>.</p><pre>cd faas</pre><p>Then we will type the command to install OpenFaaS on your Docker Swarm Cluster.</p><pre>sudo ./deploy_stack.armhf.sh</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/463/1*EQrghOid7JkJiZB2dkc2Ug.png" /></figure><p>Now let’s check to see that all of the OpenFaaS services are up and running.</p><pre>sudo docker service ls</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*vwfWVz0KYWV-bd2duZ5VVQ.png" /></figure><p>Open a browser and open the OpenFaaS UI.</p><p><a href="http://master-openfaas.local:8080/ui/">http://master-openfaas.local:8080/ui/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6uHNgzT_hYm1BxgD5KF8mw.png" /></figure><p>Congrats! You now have a Docker Swarm cluster on your RPi with OpenFaaS ready to deploy your Serverless functions.</p><h3><strong>Deploy your first function with the Function Store</strong></h3><p>Now we will deploy our first function with the function store. The function store is a collection of community built functions that you can deploy with one click.</p><p>On the OpenFaaS web interface in your browser, click on the <strong>Deploy New Function</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*nALzOF-Mm94m1pWUhkeAzA.png" /></figure><p>Select the <strong>figlet</strong> and then click the <strong>Deploy</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*08n0AyoWgqe-_QxdNeIm2Q.png" /></figure><p>Select the deployed Figlet function on the left panel, write a message in the request body, then click the <strong>Invoke </strong>button to execute the function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z2dySiAdBiKAn_xUnWDm4g.png" /></figure><p>You can also make the request use curl on the command line to make the request as well.</p><pre>curl -X POST \<br>  <a href="http://master-openfaas.local:8080/function/figlet">http://master-openfaas.local:8080/function/figlet</a> \<br>  -d &#39;Hello Again, From TEAM SERVERLESS&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/521/1*UxPESZtuLSd0WMXhaJaUJQ.png" /></figure><h3><strong>Deploy a function with the OpenFaaS CLI program.</strong></h3><p>Now that we have deployed our first function, let’s use the OpenFaaS CLI program to build and deploy a simple Golang function.</p><blockquote>The OpenFaaS CLI program was already installed on the RPi master node from PiBakery, so no additional downloads will be required. From the command line we can just call it with the <strong>faas-cli </strong>command.</blockquote><p>Log back into the RPi master node and create a directory called <strong>functions</strong> and then move into that director.</p><pre>mkdir functions &amp;&amp; cd functions</pre><p>Then use faas-cli to pull some sample templates for functions.</p><pre>faas-cli template pull</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*MQUcNoFdiP5ED13vAF0Y2g.png" /></figure><p>Next create a new function.</p><pre>faas-cli new rpi-go --lang go-armhf</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*ZBRheTKozLZncU5BDHHZkQ.png" /></figure><p>Now move into the rpi-go directory.</p><pre>cd rpi-go</pre><p>Open the handler.go file with nano.</p><pre>nano handler.go</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*Hs70lz_0hR44vFpUunqfSA.png" /></figure><p>Edit the text in the quotes to change the message to include, <strong>Welcome to TEAM SERVERLESS!!!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*eclbID_kUGcXkguCEyN2mg.png" /></figure><p>Type <strong>control-o</strong> to save the file and then <strong>control-x </strong>to exit.</p><p>Move up a directory back to the functions directory.</p><pre>cd ..</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/477/1*2-Lm_qFy3hZblFXODy7p6A.png" /></figure><p>Now build the function with the <strong>sudo</strong> command.</p><pre>sudo faas-cli build -f rpi-go.yml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*1COFw_0CISqhVCvS4KclMQ.png" /></figure><p>Now deploy the function to OpenFaaS.</p><pre>faas-cli deploy -f rpi-go.yml --gateway http://127.0.0.1:8080</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*075VqpQ0J2tL51qQ4j-Dcw.png" /></figure><p>Now call the function using curl.</p><pre>curl -X POST \<br>  http://master-openfaas.local:8080/function/rpi-go \<br>  -d &#39;I did it!&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*HMti1XHyhWfptZjJ5oRdFw.png" /></figure><p>YOU DID IT! You now have what you need to build Serverless functions quickly on your newly minted RPi Cluster.</p><h3><strong>Last Words</strong></h3><p>Please go check out the <a href="https://github.com/openfaas/faas">GitHub repository for OpenFaaS</a> and join the community. And don’t forget to <strong>star </strong>OpenFaaS on Github!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0957f4d8a49" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Take the Helm with Kubernetes on Windows]]></title>
            <link>https://medium.com/@JockDaRock/take-the-helm-with-kubernetes-on-windows-c2cd4373104b?source=rss-4f792e861d57------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2cd4373104b</guid>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[windows-10]]></category>
            <category><![CDATA[helm]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Jock Reed]]></dc:creator>
            <pubDate>Tue, 09 Jan 2018 05:27:11 GMT</pubDate>
            <atom:updated>2018-01-09T05:28:59.038Z</atom:updated>
            <content:encoded><![CDATA[<p>In the last few guides I have put out, I have been working to make it easier, for those of us using Windows 10, to be able to use container and orchestration tools for development with Kubernetes. The goal is also to remove as many of the installation head aches of installing these tools, on your Windows 10 computer, as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*C9_DRETsaoPtMde_w71I_A.png" /></figure><p>This guide will help you to install Helm, a package manager for Kubernetes, on your Windows computer. Package managers are nice when you are wanting to install dependencies quickly. Checkout this blog to hear more about making Windows simpler by using the Chocolatey package manager.</p><p><a href="https://medium.com/@JockDaRock/using-windows-do-yourself-a-favor-and-install-chocolatey-6b01e0ab2715">https://medium.com/@JockDaRock/using-windows-do-yourself-a-favor-and-install-chocolatey-6b01e0ab2715</a></p><p>Sadly, Helm, does not have a Chocolatey Package for Windows… yet. Instead, we will be installing this from the Helm site using the binary the Helm site provides provide.</p><p><strong>WHY Helm?</strong></p><p>The reason we want to install helm is to be able to easily try out and develop on cloud native applications and install them with minimal effort with Helm Charts.</p><p><strong>Pre-Requisites</strong></p><ul><li>You will need the command line program <strong>kubectl</strong> installed on your Windows 10 computer and configured to work with a Kubernetes Cluster. The easiest way to do this is to install using the Windows package manager Chocolatey, <strong>choco install kubernetes-cli.</strong></li><li>7-Zip compression / decompression program is needed to extract the Helm program for Windows from the compressed file-folder from the Helm site. You can get 7-Zip here (<a href="http://www.7-zip.org/">http://www.7-zip.org/</a>). Or if you have the Chocolatey package manager on Windows, you can use this command, <strong>choco install 7zip, </strong>to install the 7zip program quickly.</li><li>Check out my previous guides to get Kubernetes up and running with Minikube on Windows and the Chocolatey package manager.</li><li><a href="https://medium.com/@JockDaRock/minikube-on-windows-10-with-hyper-v-6ef0f4dc158c">https://medium.com/@JockDaRock/minikube-on-windows-10-with-hyper-v-6ef0f4dc158c</a></li><li><a href="https://medium.com/@JockDaRock/installing-the-chocolatey-package-manager-for-windows-3b1bdd0dbb49">https://medium.com/@JockDaRock/installing-the-chocolatey-package-manager-for-windows-3b1bdd0dbb49</a></li></ul><p><strong>Installation</strong></p><p>Download the latest version of the compressed executable from the Helm github site, <a href="https://github.com/kubernetes/helm/releases">https://github.com/kubernetes/helm/releases</a>. Click the windows link and it should download to your computer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bj6S4zz9DECZyVrLdCctlA.png" /></figure><p>Navigate to the folder you downloaded the helm-vX.X.X-windows-amd64.tar.gz compressed file from and move the file to its own directory.</p><p>Navigate to the new directory and right click on the tar.gz file and with 7Zip, open the tar.gz archive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/779/1*bRQZtoYb6CVQDwtBVnQSzw.png" /></figure><p>Double click the single tar file in that directory, <strong>helm-v2.7.2-windows-amd64.tar.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*B26qwx2Ni6gEaFpuf92kFA.png" /></figure><p>You should now see a windows file folder in the 7Zip window, <strong>windows-amd64</strong>. Right click on the folder, select Copy To, and select the directory you want to copy the folder to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/378/1*XQeUhlEIt8ZiWYv_uNETDA.png" /></figure><p>After getting the folder moved to the directory of your choice, we will add the helm program to the System File path to make it easily accessible from the command line.</p><p>Open the Control Panel’s <strong>System</strong> panel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/268/1*JfHylegBRvLa4c0U02YAsg.png" /></figure><p>Select the <strong>Advanced system settings</strong> link on the left.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/283/1*G7_YQFc5_crBBcBU7om_aQ.png" /></figure><p>Select <strong>Environment Variables</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/373/1*0Meyrj2FoafU2aauYm_B1w.png" /></figure><p>Under <strong>System variables</strong>, select <strong>Path</strong>, and then select <strong>Edit</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*JBiCJkE4xgUqH5UbB9bdWg.png" /></figure><p>Select the <strong>New</strong> button and then add the folder path where you copied the helm folder to and then press <strong>OK</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/1*vl6AyImGqSKLIbCJ75ipkg.png" /></figure><p>Helm should now be installed properly on your Windows 10 computer. Let’s check to make sure.</p><p>Open a new command line window and type <strong>helm</strong> on the command line to make sure you have access to helm from the command line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*eICp8hXaNz_7XOo1PithBw.png" /></figure><p>Assuming you have the kubectl program configured for your kubernetes cluster you can now initialize helm.</p><pre>helm init</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MfeTr8Ot5t4drLUxTQvCuw.png" /></figure><p>Now you are ready to deploy kubernetes applications to your kube cluster. Visit the KubeApps site, <a href="https://hub.kubeapps.com/">https://hub.kubeapps.com/</a>, to see what helm charts are currently available and instructions on how to install them.</p><p>Happy Helming!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2cd4373104b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Merged! My first submission to the OpenFaaS Function Store]]></title>
            <link>https://medium.com/hackernoon/merged-my-first-submission-to-the-openfaas-function-store-4a35b5cd366c?source=rss-4f792e861d57------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a35b5cd366c</guid>
            <category><![CDATA[openfaas]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[faa]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Jock Reed]]></dc:creator>
            <pubDate>Thu, 04 Jan 2018 15:39:31 GMT</pubDate>
            <atom:updated>2018-01-10T19:49:27.563Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/418/1*5Y_la5qyBJmwODm7yhBi2A.png" /><figcaption><em>Copyright </em>©<em> OpenFaaS Ltd</em></figcaption></figure><p>If you haven’t heard about <a href="https://www.openfaas.com/">OpenFaas Serverless Platform</a> and how it is changing the game in serverless you need to try it out today.</p><p>Recently, OpenFaaS has made it even simpler to get started with Serverless by releasing the <a href="https://blog.alexellis.io/announcing-function-store/">function store</a>. The function store allows for one click deployment of community built functions to show you the power of what you can build into your serverless stack. Today, I am adding my first commit to that function store for the first of a set network tools that can be used serverlessly, the nslookup function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JEDciXtQEDEa3zPRA4xVrg.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FA0UTJR7d0io%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DA0UTJR7d0io&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FA0UTJR7d0io%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a11033514835f937487b769fe72cf97e/href">https://medium.com/media/a11033514835f937487b769fe72cf97e/href</a></iframe><p>Also try out <a href="https://medium.com/u/89b4ba5a32ff">Alex Ellis</a>’ nmap function for your networking needs as well as the other community functions in the function store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*zYTGQF_kafgMjWkLxO7B1w.png" /></figure><p>Check out these videos and guides for getting started with OpenFaaS.</p><ul><li>FaaS and Furious KubeCon 2017: <a href="https://youtu.be/XgsxqHQvMnM">https://youtu.be/XgsxqHQvMnM</a></li><li>Deploy OpenFaaS on Kubernetes Sandbox Environment w/ Cisco DevNet: <a href="https://blogs.cisco.com/developer/openfaas-at-the-helm-w-kubernetes-in-the-devnet-sandbox">https://blogs.cisco.com/developer/openfaas-at-the-helm-w-kubernetes-in-the-devnet-sandbox</a></li></ul><p>And don’t forget to <a href="https://github.com/openfaas/faas"><strong>star OpenFaaS</strong></a> on Github and <strong>join the community</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a35b5cd366c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/merged-my-first-submission-to-the-openfaas-function-store-4a35b5cd366c">Merged! My first submission to the OpenFaaS Function Store</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Disabling IPv6 on Network Adapter Windows 10]]></title>
            <link>https://medium.com/@JockDaRock/disabling-ipv6-on-network-adapter-windows-10-5fad010bca75?source=rss-4f792e861d57------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fad010bca75</guid>
            <category><![CDATA[windows-10]]></category>
            <category><![CDATA[network]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[windows]]></category>
            <dc:creator><![CDATA[Jock Reed]]></dc:creator>
            <pubDate>Mon, 18 Dec 2017 16:09:40 GMT</pubDate>
            <atom:updated>2018-01-04T15:58:32.480Z</atom:updated>
            <content:encoded><![CDATA[<p>Sometimes when deploying a VM application, not all applications are using the IPv6 network protocol and depending on your environment you might have to update a network adapter to temporarily disable IPv6. This short guide will quickly run you through disabling IPv6 on a Windows 10 network adapter.</p><p><em>Note: This is meant to be a workaround for some issues that others have encountered while setting up a virtual switch for use with a HyperV Virtual Machine. I would not recommend doing this in production on a Windows server. Mainly this is to be used for development and PoC purposes.</em></p><p>First open the <strong>Network and Sharing Center</strong> by right clicking on the network icon on your Windows 10 desktop and then select <strong>Open Network and Sharing Center</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/307/1*4vcsicgHovGRnkBcwCcWtQ.png" /></figure><p>Once the Network and Sharing Center are open, on the right panel, select <strong>Change adapter settings</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/191/1*RytIBVaw1z-0WTQE9rF7CQ.png" /></figure><p>Next, right click on the network adapter you are looking to change and then select <strong>Properties</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/481/1*KtCYN7dKRN91bFK6jiC6UA.png" /></figure><p>Now, uncheck the box for <strong>Internet Protocol Version (TCP/IPv6)</strong> and then click <strong>OK</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*IUIAy0t2KA7LbT582lIVzg.png" /></figure><p>Once that is complete, you should be ready to go. Happy Windows-ing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fad010bca75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Minikube on Windows 10 with Hyper-V]]></title>
            <link>https://medium.com/@JockDaRock/minikube-on-windows-10-with-hyper-v-6ef0f4dc158c?source=rss-4f792e861d57------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ef0f4dc158c</guid>
            <category><![CDATA[minikube]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[windows-10]]></category>
            <category><![CDATA[microsoft]]></category>
            <dc:creator><![CDATA[Jock Reed]]></dc:creator>
            <pubDate>Sat, 16 Dec 2017 10:05:49 GMT</pubDate>
            <atom:updated>2018-01-05T15:20:33.729Z</atom:updated>
            <content:encoded><![CDATA[<p>Getting started with Kubernetes can be daunting when you don’t know where to begin. Luckily the folks at Kubernetes have a great platform you can run locally on your laptop. This will setup up a basic test bed for kubernetes called Minikube. I will quickly walk you through getting up and running with minikube.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UBwQRP_HpjawvPzlvdHfWw.jpeg" /></figure><p><strong>Pre-reqs before getting started</strong></p><ul><li>Windows package manager, <a href="https://chocolatey.org/">Chocolatey</a>. (<a href="https://medium.com/@JockDaRock/installing-the-chocolatey-package-manager-for-windows-3b1bdd0dbb49">Go here for a guide to install chocolatey</a>)</li><li>Hyper-V installed on your Windows 10 machine. (<a href="https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v">Use this guide to get Hyper-V installed</a>)</li></ul><p><strong>Installation</strong></p><p>Open a command line window with administrator privileges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*cKHzofShesGhOmhOzeT2Eg.png" /></figure><p>Then use the chocolatey package manager to install minikube.</p><pre>choco install minikube</pre><p>Next install the kubernetes command line program with the chocolatey package manager.</p><pre>choco install kubernetes-cli</pre><p>Once that is installed you will need to make some changes to the Windows Hyper-V manager. I will not get into the reasons why we need to make some of these changes, but the short answer is so you don’t have to do more work to run this along side other software packages like Docker-For-Windows that also use Windows Hyper-V, seamlessly.</p><p>Open the Hyper-V Manager.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*BDkfXerXSUMttd2IU0VL9g.png" /></figure><p>Once in the Hyper-V Manager, on the right panel, select the Virtual Switch Manager.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*FVb8sfWZMlXrT9i0Xtbb_g.png" /></figure><p>Next we will create a virtual switch for minikube. Select <strong>New virtual network switch </strong>on the right hand side, select <strong>External </strong>for the network type, and then press the <strong>Create Virtual Switch</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*xwFelgX0H_c91tBknDu-_w.png" /></figure><p>Name the switch <strong>Primary Virtual Switch</strong> and click the apply button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*71ynSa77g4npuQXHJvPNrw.png" /></figure><p>Once you have the switch created we are now ready to start minikube. Run the following command to start the minikube VM with our applied changes.</p><pre>minikube start --vm-driver hyperv --hyperv-virtual-switch &quot;Primary Virtual Switch&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/715/1*3MuYyS4meXm59O_0xwgfFA.png" /></figure><p>Once the VM is running we will have two more steps to do to address a bug in minikube for Windows. We need to turn off Dynamic Memory for the minikube VM. There is bug reported on this issue which can be <a href="https://github.com/kubernetes/minikube/issues/2326"><strong>found here</strong></a><strong>. </strong>Once this bug has been resolved, I will update the instructions here.</p><p>In your administrator command line window stop the minikube VM with the following command.</p><pre>minikube stop</pre><p>Once minikube has stopped, open the Hyper-V Manager again and right click on the minikube VM and select settings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*g4btrIldO_U0WNNDmTs-fg.png" /></figure><p>Select the <strong>Memory</strong> option on the left panel, then de-select <strong>Enable Dynamic</strong> <strong>Memory</strong>, and then click <strong>Apply</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*2oOZj3kxuZXEEJBo99HsVg.png" /></figure><p>Close Hyper-V manager and then return to the administrator command line window and restart minikube.</p><pre>minikube start</pre><p>Once minikube is restarted you should be ready to go. We will confirm the installation is ready by checking a couple of things.</p><p>In the command line window, enter the following command.</p><pre>kubectl get pods -n kube-system</pre><p>You should see the following result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*LfRnLyiuMWO1DfhuQzsAVg.png" /></figure><p>If you are a little more visual and want to see the kubernetes dashboard, you can open that up by typing in the following command in the command line window.</p><pre>minikube dashboard</pre><p>That will open up the dashboard window in your default browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F3C6rW8T177KeKJRVH_NFA.png" /></figure><p>Now you are ready to explore and start your journey to learning Kubernetes.</p><p><strong>Side Note on IPv6 Networking and Minikube on Windows 10</strong></p><ul><li>I got some feedback that some users were experiencing a problem with IPv6 networking. There are some cases where minikube will not work with the network switch we created earlier in this guide. To correct this you will need to disable IPv6 protocol if this is the case. <a href="https://github.com/kubernetes/minikube/issues/754#issuecomment-340315883">The IPv6 issue is reported on GitHub</a>.</li><li>The following guide will help you quickly disable IPv6: <a href="https://medium.com/@JockDaRock/disabling-ipv6-on-network-adapter-windows-10-5fad010bca75">https://medium.com/@JockDaRock/disabling-ipv6-on-network-adapter-windows-10-5fad010bca75</a></li></ul><p>If you would like to take your Kubernetes experience to the next level, try reserving a free sandbox lab environment for Kubernetes from <a href="https://developer.cisco.com/site/sandbox">Cisco DevNet Sandbox</a>. Use the following guides to get started with Kubernetes in DevNet Sandbox.</p><ul><li><a href="https://medium.com/@JockDaRock/youre-welcome-production-grade-kubernetes-in-a-private-secure-environment-for-free-5ba80c278932">You’re Welcome — Production Grade Kubernetes in a private, secure environment for Free</a></li><li><a href="https://blog.devnetcreate.io/serverless-at-the-helm-in-kubernetes-in-the-devnet-sandbox-2038031a3f4b">OpenFaaS At The Helm w/ Kubernetes in the DevNet Sandbox</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ef0f4dc158c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>