Dwayne Williams

Just figured it out. You run the curl command from one of the nodes. If you did the same as me you ran it on master. Edit: It only worked...

It has to do with the iptables of the pis that are preventing them from communicating. They have to be using leagcy binaries these three commands solved my problem: sudo...

You are correct @justinabrahms but they should all be on the sames network in kubernetes so any node should be able to hit a cluster ip, which wasn't happening here....

Wait... Those may be the wrong commands though.. One moment. Ill double check

I'm sorry you are right those were the wrong commands. you want these: ``` sudo update-alternatives --set iptables /usr/sbin/iptables-legacy sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy sudo update-alternatives --set ebtables /usr/sbin/ebtables-legacy ```...

I found my problem was just low specs. I was running it on a 1GB Ram and 1Core CPU virtual machine. beefed that up a little to 4GB Ram and...

@pablogs9 Thanks for the reply! Not sure what you mean by "you need to implement lockings in middleware". Is there more that this file needs or is it just copying...

Yes. looks like the pico sdk does support mutex, lock and semaphore https://raspberrypi.github.io/pico-sdk-doxygen/group__pico__sync.html. So i guess i need to implement the contents of the multithread.c using the pico sdk library?

Sure, I'll get on that