Deploying the UniFi SDN Controller on Kubernetes | Blog

[giscus[bot]]

Deploying the UniFi SDN Controller on Kubernetes | Blog

Run the UniFi SDN controller on Kubernetes using Ingress Nginx

https://blog.stabl.one/posts/006-unifi-controller-kubernetes/

[Hr46ph]

Thank you! I've been migrating my docker apps from a single docker node to a 7 node kubernetes cluster. This is one of the last ones and this is very helpful. I do have a few questions if you don't mind :P.

I see you left out these ports and I wonder why:
UDP 10001 Used for device discovery.
UDP 1900 Used to "Make application discoverable on L2 network" in the UniFi Network settings.

10001 in particular I think is important when you want new devices that are adoptable to pop up in Unifi controller UI.

Then about the /tmp volume mount point, can you explain why you did that? I never used that on Docker and this page makes no mention either, so I wonder why you decided to use it:
https://github.com/jacobalberty/unifi-docker?tab=readme-ov-file#volumes

You decided not to separate /unifi/data/backup. Personally I would want to keep that on its own PV but I guess its a matter of opinion whether that matters (and whether you actually use the autobackup feature). A mention of it would be nice and why you decided not to use it.

Last but not least, what happened to MongoDB and its volume?

Thanks for the writeup, very helpful. Even more so if you could shed some light on these questions :D .

Cheers!

[StefanAbl]

Thank you for taking the time to read and being the first to comment.

I left out these ports because I don't really need them. For easy adoption I prefer to use DHCP Option 43, since my cluster is also on a separate subnet than the management interfaces of my Unifi devices. See: https://help.ui.com/hc/en-us/articles/204909754-UniFi-Network-Remote-Adoption-Layer-3
If you want to include them you'll have to add them just like the STUN port.

Mounting the /tmp directory is usually necessary when using the option readOnlyRootFilesystem as otherwise the application won't be able to write its temporary files into the directory.

Mounting the backup directory can definitely make sense if you want to treat it separately, but for me all PVs are replicated via longhron and backed up externally by it.

MongoDB is bundeled inside the image and it's data is also in the directory /unifi. you can also run it separately, but I chose not to for simplicity.

Thanks again for reading and commenting and congrats on your cluster.

Cheers

[Hr46ph]

Awesome. Thanks for taking the time to reply!

I could probably use DHCP option 43 as well, never knew about that :) .

I'm using Longhorn as well, I'll be testing backup / restore for Unifi later today and if that works fine, I won't need to separate the autobackup directory. I already tested removing / redeploying Unifi and it picks up the volumes so I expect no problems after a restore.

Cheers!