Node Port vs Cluster IP Kubernetes | DevOps | Interview | Tech Arkit

Node Port vs Cluster IP Kubernetes | DevOps | Interview | Tech Arkit

Join WhatsApp: https://chat.whatsapp.com/HXdVV6QhsHY...

Join this channel to get access to un-published video content:
   / @techarkit  

Follow Us on Social Media
👉 WhatsApp Group: https://bit.ly/TechArkitWhatsAppGroup
✅ Join Telegram Group: http://t.me/linuxarkit 3000 Members Joined
☑ GitHub: https://github.com/techarkit/
👀 FB Private Group: 5K members   / techarkit  
⚛ Facebook:   / techarkit  
☯ Twitter:   / tech_arkit  
♨ Instagram:   / arkit.co.in  
✌ Patreon:   / techarkit  
🌏 Website: https://arkit.co.in
☘ Blog: https://techarkit.blogspot.com/
✓ Reddit:   / techarkit  
🚩 Tumblr Blog: https://www.tumblr.com/blog/techarkit
🏁 Email: aravikumar48[at]gmail.com
🎌 Quora: https://www.quora.com/q/cxfarqipmxzaj...

Post your topic, and we will make videos for you
🏳 https://forms.gle/M4ysoMNh1zsPXiw89

#techarkit #devops #interview

NodePort:

NodePort is a type of service that exposes a service on a specific port of each node in the cluster.
When you expose a service using NodePort, Kubernetes will allocate a specific port on every node in the cluster (usually in the range 30000-32767) and any traffic sent to this port will be forwarded to the corresponding service.
NodePort is typically used when you need to access a service from outside the Kubernetes cluster, for example, to expose a web application to the internet.

ClusterIP:

ClusterIP is a type of service that exposes a service on an internal IP address that is only reachable from within the Kubernetes cluster.
This is the default type of service in Kubernetes.
ClusterIP is used for communication between services within the cluster.