Kubernetes DNS Horror Stories - And How to Avoid Them

Kubernetes DNS Horror Stories - And How to Avoid Them

CNCF [Cloud Native Computing Foundation] via YouTube Direct link

Upstream DNS issue

24 of 29

24 of 29

Upstream DNS issue

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Kubernetes DNS Horror Stories - And How to Avoid Them

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Datadog
  3. 3 Challenges
  4. 4 What we did not expect
  5. 5 Outline
  6. 6 How it works (by default)
  7. 7 Accessing DNS
  8. 8 Theory: Scenario 2
  9. 9 In practice
  10. 10 Let's disable IPv6!
  11. 11 What triggers IPv6?
  12. 12 We use Go a lot
  13. 13 Subtle difference
  14. 14 CGO implementation
  15. 15 Coredns Autopath
  16. 16 Node-local-dns
  17. 17 Initial state
  18. 18 Pod A deleted
  19. 19 Source port reuse
  20. 20 Mitigation #2
  21. 21 Coredns getting OOM-killed
  22. 22 Proportional autoscaler
  23. 23 Staging fright on AWS
  24. 24 Upstream DNS issue
  25. 25 Something weird
  26. 26 DNS is broken for a single app
  27. 27 Sometimes it's not DNS
  28. 28 Our DNS setup
  29. 29 Conclusion • Running Kubernetes means running DNS DNS is hard, especially at scale

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.