Static IP's for Apps

[PatrickStuartMoney]

Hello to anyone who can help!

I've been a Truenas Core user for a few years now and had the hang of jails and their setups. Had it the way I wanted but my overall NAS started to fail so I've upgraded and moved over to SCALE thinking it would be a good experience.

In trying to mimic my CORE setup I've just exhausted myself trying to figure out how to get apps to work as I had them in CORE.

Each app with it's own IP address so I can manage them individually and directly.

Right now my only focus is getting apps, either from Official Charts, Truecharts or building a Docker image to have it's own IP.

I've been down the rabbit hole and looked into Metallb as it's popped up a few times as the work around.

I've tried installing the Metallb app via TrueCharts and via Docker Image, it keeps getting stuck in "deploying" I didn't know if this was the norm so I tried running:

k3s kubectl get svc -A

which gave the below:

NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default kubernetes ClusterIP 172.17.0.1 <none> 443/TCP 197d
kube-system kube-dns ClusterIP 172.17.0.10 <none> 53/UDP,53/TCP,9153/TCP 197d
cert-manager cert-manager ClusterIP 172.17.100.83 <none> 9402/TCP 8d
cert-manager cert-manager-webhook ClusterIP 172.17.169.135 <none> 443/TCP 8d
metallb-system webhook-service ClusterIP 172.17.182.116 <none> 443/TCP 8d
prometheus-operator prometheus-operator ClusterIP None <none> 8080/TCP 8d
kube-system kubelet ClusterIP None <none> 10250/TCP,10255/TCP,4194/TCP 8d
ix-transmission transmission LoadBalancer 172.17.20.90 <pending> 10109:29896/TCP 66m
ix-transmission transmission-torrent LoadBalancer 172.17.13.34 <pending> 51414:63114/TCP,51414:63114/UDP 66m

I see my one tester app transmission in there and EXTERNAL IP is <pending>

I can see metallb-system running but! The app never deploys, is metallb the default loadbalancer in SCALE?

I also checked to see what POD's were running and it's there too:

metallb-system pod/speaker-lg75w 1/1 Running 0 161m 192.168.2.93 ix-truenas <none> <none>
metallb-system pod/controller-84d6d4db45-qzmvq 1/1 Running 0 3h14m 172.16.1.190 ix-truenas <none> <none>
ix-transmission pod/transmission-5646d9b44b-nsp44 1/1 Running 0 3h14m 172.16.1.192 ix-truenas <none> <none>

If it is the default load balancer, how do I edit its settings so it can assign IP's to my apps?

Thanks.

 

[PatrickStuartMoney]

Seems building the apps via Docker Launcher gives the ability to have their own IP's just doesn't allow for persistent storage for the apps configs.

One step further at least!