Part 4 | RTF Series | DNS Overview

In an environment where containers can scale up and down frequently we cannot rely on IP addresses of pod to access them. To solve this problem K8s offers clusterIP service that spans across all the nodes and gives a static IP interface to the pod. However giving static IP is not enough, as a developer I would want standard domain name that's easy to remember. To address this requirement kubernetes offer core-dns that creates domains pointing to clusterIP address. Apart from this, as we are using appliance model of RTF there is yet another DNS service that is a superset and forms the part of the planet container. In this video lets get an overview of all the DNS service involved.
Note: Planet container is part of Appliance RTF, you will not find this container in BYOK RTF.
⏱ Video Timestamps
==========================
0:00 Start
0:18 DNS Overview in RTF
4:48 DNS resolution flow using K8s core-dns
9:50 Handson: Validating planet containers core-dns service
12:15 Handson: Exploring kube-system DNS
21:00 Entering a pod and validating the DNS resolver
📌 Pre-requisite Content
==========================
🔗 RTF Primer Part 1 [Virtualization & Containerization]: • Part 1 | RTF Primer | ...
🔗 RTF Primer Part 2 [Kubernetes Basics]: • Part 2 | RTF Primer | ...
📌 Previous/Next Parts in this series
=================================
🔗 RTF Series Part 1 [RTF Architecture]: • Part 1 | RTF Series | ...
🔗 RTF Series Part 2 [Appliance Installation]: • Part 2 | RTF Series | ...
🔗 RTF Series Part 3 [Pods, Namespaces, Services and Cronjobs]: • Part 3 | RTF Series | ...
🔗 RTF Series Part 4 [DNS Overview]: • Part 4 | RTF Series | ...
🔗 RTF Series Part 5 [App Deployment Flow]: • Part 5 | RTF Series | ...
🔗 RTF Series Part 6 [Ingress config for Appliance RTF]: • Part 6 | RTF Series | ...
🎬 RTF Series Playlist
=====================
💥 • Runtime Fabric
📌 Similar Content
==========================
🔗 Transactions in Mule 4: • Mule 4 | XA | Local Tr...
🔗 Classloading Isolation in Mule 4: • Refined Error handling...
🔗 API Design Best Practices: • API Design | Best Prac...
🔗 Custom Policy: • Mule 4: Create Custom ...
🔗 API Gateway and Autodiscovery: • Mule 4: API Gateway an...
🔗 Global Error Handler: • Mule 4: Create a Globa...
🎬 Popular Mule 4 Playlists
==========================
💥 Advanced Concepts in Mule: bit.ly/AdvancedMule
💥 Mule 4 Custom Connectors: bit.ly/Mule4CustomConnectors
💥 Dataweave Series: bit.ly/dataweave2
Let's connect:
=========================
💥 Twitter: / vishwas_p13

[@alaaabdelfattah3126]

Thank you, again Very detailed explanation

[@luismesquita6528]

Kudos for your work Vishwas as you really excel in this series. Really enjoy that you clarify conditional scenarios and do in depth detailed analysis.

[@jacekbiaecki8076]

Very detailed explanation. Love it

[@ankurkushwaha5150]

thanks Vishwas sir ,Actually I forgot the name of your channel , after that I search one keyword "concurrency and RTF in mulesoft" , I know there is only one mentor who explained that topic in youtube . and I got your video at first in search index.

[@AltrozMotor]

How we configure vanity domain ?

[@Vishwasp13]

You need to have ingress configured for it, then you can directly create a domain name for your controllers public IP/private IP address via public/private DNS based on your requirement.
Alternatively, you can front your controller using a network load balancer and assign a domain to your Network Load Balancers public/private IP address via public/private DNS.

[@AltrozMotor]

@@Vishwasp13 Thank you