When I try to create it, it gives the following error:
The Service "kamailio" is invalid.
spec.ports[1].nodePort: invalid value '5060', Details: provided port is already allocated
It appears that the error checking kubernetes does of the service manifest isn't taking into account that udp and tcp ports are different ports. If i run it through and change the tcp ports to one port higher, it works.
I discussed the possible bug with the kubernetes developers and they had this to say:
justinsb [8:17 PM]
@xwhyz: I think it’s actually a bug/design mistake (my mistake) that we don’t allow you to bind the same NodePort for both TCP & UDP
[8:18]
It’s not a huge deal if you have ELB in front, because it will redirect the ports anyway
[8:19]
Not sure what to recommend if you’re not using ELB though
[8:19]
It’s definitely a fixable bug. Though likely not in 1.2
the following manifest is working, but doesn't meet the sip standards as i understand them:
it seems the best fix for this situation after some discussion with the kubernetes dev's is to add some rules to iptables to direct the traffic to come in from the correct ports, but obviously we're looking for the best solution to the problem
We have the following service manifest for kamailio:
When I try to create it, it gives the following error:
It appears that the error checking kubernetes does of the service manifest isn't taking into account that udp and tcp ports are different ports. If i run it through and change the tcp ports to one port higher, it works.
I discussed the possible bug with the kubernetes developers and they had this to say:
the following manifest is working, but doesn't meet the sip standards as i understand them:
Here is the output of kubectl describe svc kamailio