Port name conflicted

[fredlubrano]

Hello,

I don't understand why it puts me that I have a conflicting port :

root@truenas[~]# k3s kubectl get service -A
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default kubernetes ClusterIP 172.17.0.1 <none> 443/TCP 35d
kube-system kube-dns ClusterIP 172.17.0.10 <none> 53/UDP,53/TCP,9153/TCP 35d
ix-mino mino-minio NodePort 172.17.238.142 <none> 9000:9000/TCP,9002:9002/TCP 34d
ix-fortianalyzer fortianalyzer-ix-chart NodePort 172.17.167.151 <none> 514:9514/TCP,514:9514/UDP,443:9433/TCP,22:9022/TCP 21s

Nov 07 07:40:59 truenas.local k3s[187588]: I1107 07:40:59.556681 187588 helpers.go:343] "Port name conflicted, it is defined more than once" portName="any-TCP-:514:0"
Nov 07 07:41:00 truenas.local k3s[187588]: I1107 07:41:00.559716 187588 helpers.go:343] "Port name conflicted, it is defined more than once" portName="any-TCP-:514:0"

"Env": [
"FORTIANALYZER_IX_CHART_PORT_443_TCP_ADDR=172.17.167.151",
"KUBERNETES_PORT_443_TCP=tcp://172.17.0.1:443",
"KUBERNETES_PORT_443_TCP_ADDR=172.17.0.1",
"FORTIANALYZER_IX_CHART_SERVICE_PORT_IX_FORTIANALYZER_9514_0=514",
"FORTIANALYZER_IX_CHART_PORT_514_TCP_PROTO=tcp",
"FORTIANALYZER_IX_CHART_PORT_22_TCP_ADDR=172.17.167.151",
"KUBERNETES_PORT_443_TCP_PORT=443",
"FORTIANALYZER_IX_CHART_PORT_514_TCP_ADDR=172.17.167.151",
"FORTIANALYZER_IX_CHART_PORT_22_TCP=tcp://172.17.167.151:22",
"FORTIANALYZER_IX_CHART_PORT_22_TCP_PORT=22",
"KUBERNETES_SERVICE_HOST=172.17.0.1",
"KUBERNETES_SERVICE_PORT=443",
"FORTIANALYZER_IX_CHART_SERVICE_PORT_IX_FORTIANALYZER_9514_1=514",
"FORTIANALYZER_IX_CHART_SERVICE_PORT_IX_FORTIANALYZER_9022_3=22",
"FORTIANALYZER_IX_CHART_PORT_514_UDP_ADDR=172.17.167.151",
"KUBERNETES_PORT=tcp://172.17.0.1:443",
"FORTIANALYZER_IX_CHART_SERVICE_PORT=514",
"FORTIANALYZER_IX_CHART_SERVICE_PORT_IX_FORTIANALYZER_9433_2=443",
"FORTIANALYZER_IX_CHART_PORT_514_TCP=tcp://172.17.167.151:514",
"FORTIANALYZER_IX_CHART_PORT_443_TCP_PORT=443",
"KUBERNETES_SERVICE_PORT_HTTPS=443",
"FORTIANALYZER_IX_CHART_SERVICE_HOST=172.17.167.151",
"FORTIANALYZER_IX_CHART_PORT_514_UDP=udp://172.17.167.151:514",
"FORTIANALYZER_IX_CHART_PORT_443_TCP_PROTO=tcp",
"FORTIANALYZER_IX_CHART_PORT=tcp://172.17.167.151:514",
"FORTIANALYZER_IX_CHART_PORT_514_UDP_PORT=514",
"FORTIANALYZER_IX_CHART_PORT_22_TCP_PROTO=tcp",
"KUBERNETES_PORT_443_TCP_PROTO=tcp",
"FORTIANALYZER_IX_CHART_PORT_514_TCP_PORT=514",
"FORTIANALYZER_IX_CHART_PORT_514_UDP_PROTO=udp",
"FORTIANALYZER_IX_CHART_PORT_443_TCP=tcp://172.17.167.151:443"
],
.../...
"Labels": {
"annotation.io.kubernetes.container.hash": "3bed1f73",
"annotation.io.kubernetes.container.ports": "[{\"containerPort\":514,\"protocol\":\"TCP\"},{\"containerPort\":514,\"protocol\":\"TCP\"},{\"containerPort\":443,\"protocol\":\"TCP\"},{\"containerPort\":22,\"protocol\":\"TCP\"}]

 

[morganL]

It's useful to explain the background... what was working and when did the error message appear. Was there a specific App/Chart that was loaded?

 

[fredlubrano]

HI Morgan,

the context is simple, I want to do a Nat TCP/514 in addition to UDP/514

Thanks

fred

 

[morganL]

The context is rarely simple... we have no idea what is running on the system and whether other Apps are working.
Without that information, we have no idea whether there is a bug or a configuration error... most of the time (not all), its a configuration issue, but we need clues to solve and help.

I don't thinks its relevant,, but the mapping of 443 to 9433 is probably not what you intended.

 

[fredlubrano]

Hello Morgan,

Thanks for the repply, the deployment is simple.
I map the following ports:

- TCP/9443 to TCP/443
- TCP/9022 to TCP/22
- TCP/9514 to TCP/ 514
- UDP/9514 to UDP/514

View node, :

what do you need ? do you want to reproduce the problem?

Thanks for the helps

fred

 

[morganL]

So the issue is mapping both TCP and UDP 514 to 9514?
Just mapping on of them is fine?

We want to narrow it down to the simplest thing thta doesn't work.... and see if anyone else has the issue.