Here is the Kubernetes dashboard for the cluster:
![dashboard](https://i0.wp.com/erudicon.com/wp-content/uploads/2018/10/k8s-dashboard.png?resize=525%2C418&ssl=1)
Here is the Kubernetes dashboard for the cluster:
I’ve updated my Kubernetes cluster so that the Raspberry Pis are now isolated from the rest of my home network and all the components are running off an Anker 10 port USB Charging Hub. This included the following additions:
This should make the whole setup somewhat more portable.
The addition of the 10 port USB charging hub allowed me to eliminate nine AC adapters and two power strips.
I’m thinking about purchasing a cheap carrying case with a foam insert so I can cart the whole thing around.
Patience is a virtue! Finally there are released versions of Kubernetes, Docker, and Weave that actually work together on the Raspberry Pi!
So when I said I had Kubernetes running on a four node Raspberry Pi 3 B+ cluster, I didn’t realize how complex a task it would turn out to be!
I had been following the instructions by Alex Ellis, but it turns out the latest version of Docker and Kubernetes doesn’t run well on the RPi 3 B+. I had to downgrade them to previous versions.
Then there were issues with the network stack. I tried Weave as recommended by Alex, but that didn’t work, so I switched to Flannel. I was then able to get the markdown to HTML converter example running. However, when I went to try setting up a dashboard I couldn’t get that to run because of issues with Flannel. Maybe I’ll try Calico next?
As for the hardware, I’ve added three more Pi’s to make a seven node cluster (one master and six workers).
I’ll have to spend some more time searching google and reading the K8s documentation to figure this one out.
I’ve started on a new project: To learn more about containers. Specifically, Docker and Kubernetes.
To do so I’ve built a small Kubernetes Cluster using four Raspberry Pi 3 B+s (see below). Eventually, I would like to expand it to seven Raspberry Pis.
I’ve been following the instructions created by Alex Ellis.
So far I have the cluster up and running. Now it’s time to do some more reading!
-Neil
All of my NTP servers are finally up and running! (For real!)
I had been having issues with the Sparkfun Trimble GPS Module and I finally contacted Sparkfun. They responded quickly and knew exactly what the issue was.
Turns out, the width of the pulse on the Pulse-per-second output of the Trimble is too short for the Raspberry Pi 2 to detect.
Sparkfun provided step by step instructions on how to download Trimble’s GPS Configuration software, connect the module to my computer, and reprogram the pulse width. Thank you Sparkfun!
So now I can finally be collecting statistics on all five modules. I’d like to get a least a week of data before beginning comparisons.
Stay tuned for more!
Well I have all five GPS modules connected and powered on!
I’m back from Field Day and the Fourth of July. I finally received my SparkFun Trimble GPS module and have it up and running.
I’m still waiting on the last GPS module, from Uputronics, before I begin comparison testing.
To setup each Raspberry Pi 2 as a Stratum 1 NTP server I’m following the recipe created by David Taylor. While the recipe is very thorough and complete, I ran into an issue disabling the login prompt on the Raspberry Pi’s serial port under Debian Jessie. No matter what I did the login prompt would always be re-enabled after the Pi rebooted. This resulted in GPSD not starting correctly. Read on to find out how to resolve the issue. Continue reading “Sunday Geek Project: Raspberry Pi NTP Server Recipe”
Here are the different GPS Modules I’m playing with or plan to play with: Continue reading “Sunday Geek Project: The Contenders and Setup”
You must be logged in to post a comment.