Routing RTMP(S) with TCPIngress

I’m running into some issues configuring Kong to handle RTMP traffic (port 1935). I’ve installed Kong via Helm with these proxy settings to open the port:

proxy:
  stream:
    - containerPort: 1935
      servicePort: 1935
      # Additional listen parameters, e.g. "ssl", "reuseport", "backlog=16384"
      # "ssl" is required for SNI-based routes. It is not supported on versions <2.0
      parameters: ["ssl"]

Then in my application chart, I add a TCPIngress configuration for the RTMP service:

{{- $fullName := include "dios.fullname" . -}}
apiVersion: configuration.konghq.com/v1beta1
kind: TCPIngress
metadata:
  name: {{ include "dios.fullname" . }}-ingress-rtmp
  labels:
    {{- include "dios.labels" . | nindent 4 }}
  annotations:
    kubernetes.io/ingress.class: kong
spec:
  {{- if .Values.ingress.tls }}
  tls:
    {{- range .Values.ingress.tls }}
    - hosts:
        {{- range .hosts }}
        - {{ . | quote }}
        {{- end }}
      secretName: {{ .secretName }}
    {{- end }}
  {{- end }}
  rules:
    {{- range .Values.ingress.hosts }}
    - host: {{ .host | quote }}
      port: 1935
      backend:
        serviceName: {{ $fullName }}-rtmp
        servicePort: 1935
    {{- end }}

I can confirm the port is open with nc -z host.name 1935, but attempting to connect to rtmp://host.name or rtmps://host.name fails silently (no logs from the kong proxy service). I’m attempting to connect with OBS, and the error is gives is:

Any suggestions? Even getting an error message out of Kong would help me to start tracking down where the problem is.

Thanks!


© 2019 Kong Inc.    Terms  •  Privacy  •  FAQ