I wanted to share a success story with a 3-way Jetson Nano k8s cluster running the deepstream-l4t image with a pod deployment that consumes four Ubiquiti g3-flex cam rtsp streams and outputs a tiled rtsp stream after object detection and tracking.
This is running k8s 1.18.1 (latest) with metallb for load balancing, flannel for networking (i gave up on calico after a day of headaches), and i’m using the nvcr.io/nvidia/deepstream-l4t:4.0.2-19.12-samples image since it has deepstream-app and was easy to get working as a hello-world kind of thing.
Jetson Nanos do spontaneously reboot presumably from heat as turning up a box fan next to them seems to help. The heatsink should probably come with a fan by default. K8s doesn’t really detect that as a NotReady condition on the node without tuning (TODO) though on AWS or other cloud platforms, it detects such a condition in seconds. I’m using Readiness and Liveness probes to try to reschedule the pod when this happens.
I have to say Metropolis and Deepstream are amazing. Wish I could buy some newer carrier boards with the dual camera interfaces, those were released a couple weeks after I bought this hardware.
Anyway, ask me anything! :)