Closed seanthewebber closed 1 year ago
Hello @seanthewebber, I'm trying to replicate, but I can't.
But I don't think the ClusterIP
is the issue here.
In the above output of k3s kubectl get service -A
that you shared, I don't see any conflicts (and specifically no port 32400
at all).
NodePort binds ports on the host, so there would be conflicts if 2 services tried to bind the same NodePort.
ClusterIP binds the port only on the POD and each POD has a different IP address, so it shouldn't have any port conflicts on that front. But I saw that you said it stays in Deploying 0/2
. Which is not something that should happening. Is the 2
a typo?
Normally it should be 1
. If that's not a typo. Then this is the cause of the port conflict. But still I don't see how this could happen
Also I understand that this is not fresh installs but existing installs trying to change ports, is that correct?
Did you, by any chance, any of those applications, had previously enabled host network?
And lastly, can you confirm if the Upgrade Policy
is set to Kill existing pods before creating new ones
?
Thanks
@seanthewebber I'm closing this as I can't reproduce it and a potential fix for your issue is already merged. However if you still experience this issue, please let me know. Thanks
Version: TrueNAS-SCALE-22.12.1
Steps to reproduce:
1.
plex
applicationplexmediaserver-1
32401
2.plex
applicationplexmediaserver-2
32402
3.Active
4.Deploying 0/2
[EFAULT] Failed to update chart release: Error: UPGRADE FAILED: failed to create resource: Service "plexmediaserver-2-tcp" is invalid: spec.ports[0].nodePort: Invalid value: 32400: provided port is already allocated
Expected result:
Both instances should launch listening on two respective ports,
32401/TCP
and32402/TCP
.Actual result:
The
plexmediaserver-2
fails to deploy due to a nodePort collision.Additional information:
The port collision is apparent by issuing a get on active services:
The pod
plexmediaserver-2-udp
remains inClusterIP
type which is conflicting with the ports of podplexmediaserver-1-udp
. If the UDP ClusterIP service type were changed toNodePort
, this issue should be resolved.Why?
I am attempting to run two Plex servers on the same TrueNAS SCALE installation. This is because a friend is colocating their resources with mine, and they will retain administrator rights to their own instance.