When working with Kubernetes Service, you will come across some of the following terminologies:
Take a look at following spec defining a sample service:
apiVersion: v1 kind: Service metadata: name: order-service spec: ports: - port: 8080 targetPort: 8170 nodePort: 32222 protocol: TCP selector: component: order-service-app
Pay attention to some of the following in above spec:
This is ipTables in Kubernetes which does the magic. It maintains the mapping of nodePort vs targetPort. K8s Kube-Proxy uses the ipTables to resolve the requests coming on a specific nodePort and redirect them to appropriate pods.
In this blog, you would get to know the essential mathematical topics you need to…
This blog represents a list of questions you can ask when thinking like a product…
AI agents are autonomous systems combining three core components: a reasoning engine (powered by LLM),…
Artificial Intelligence (AI) has evolved significantly, from its early days of symbolic reasoning to the…
Last updated: 25th Jan, 2025 Have you ever wondered how to seamlessly integrate the vast…
Hey there! As I venture into building agentic MEAN apps with LangChain.js, I wanted to…
View Comments
it should be "When working with Kubernetes SERVICE" and not "When working with Kubernetes Pod"