Customizing Kubernetes DNS using Consul to scale Nginx RTMP

1. Chen Fisher
VP R&D

2. Internal & Confidential 22

3. Internal & Confidential

4. Internal & Confidential

5. Internal & Confidential

6. Internal & Confidential

7. Internal & Confidential

8. Internal & Confidential

9. Internal & Confidential

10. Internal & Confidential

11. Internal & Confidential

12. Internal & Confidential

13. Internal & Confidential

14. Internal & Confidential

15. Internal & Confidential

16. Internal & Confidential

17. Internal & Confidential
Pulling stream from one nginx to another
17

18. Internal & Confidential
How can we find the nginx holding our stream?
18

19. Internal & Confidential
What we’re going to do
19
●Launch a Consul cluster using Helm (and have it with a fixed IP address)
●Configure Kube-DNS to use Consul as a custom dns (stub domains)
●For every stream published to Nginx create a DNS record
●When playing a stream, use its unique FQDN to have it resolved to the
right Nginx IP address by our DNS

20. Internal & Confidential
Consul cluster
20

21. Internal & Confidential
Setting fixed IP
address for
Consul
IP: 100.64.0.11
Port: 53 -> 8600
21

22. Internal & Confidential
kube-dns
Configure kube-dns to use Consul as custom DNS
kubedns, dnsmasq and healthz
22

23. Internal & Confidential
ConfigMap
Set stub domain
consul -> 100.64.0.11
For example:
something.service.consul
23

24. Internal & Confidential
Register a stream
For every published stream we register the Nginx instance with
Consul
24

25. Internal & Confidential
Consul Agent vs Catalog
Multiple Agents (agent per host)
Single Catalog
25

26. Internal & Confidential
Registering a stream
“dns” as fictitious node
name
$name as service name
Will be resolved from
$name.service.consul
LOCAL_IP as the ip
address of Nginx
26

27. Internal & Confidential
Query for a stream
Resolve $name.service.consul
27

28. Internal & Confidential
Querying for a stream
Resolving
$name.service.consul
28

29. Internal & Confidential

30. Internal & Confidential
FIN
30