Kubernetes Service 有 ClusterIP、NodePort 和 LoadBalancer 三種類型，分別適用于內部通信、基礎外部訪問和云環(huán)境下的公網服務。ClusterIP 是默認類型，僅提供集群內部訪問；NodePort 在所有節(jié)點上開放指定端口，適合簡單測試；LoadBalancer 適用于云平臺，自動創(chuàng)建負載均衡器并分配外網 IP，適合生產環(huán)境的公網訪問。

Kubernetes Service is a way to expose an application running on a set of Pods as a network service. Since Pods are ephemeral — they can come and go — Services provide a stable endpoint for accessing your app, no matter how the underlying Pods change.

There are several types of Services in Kubernetes, each designed for a specific use case. The most common ones are ClusterIP, NodePort, and LoadBalancer.

What is ClusterIP?

ClusterIP is the default type when you create a Service without specifying one. It gives your Service an internal IP address that’s only accessible within the cluster.

This is great for communication between services inside your Kubernetes environment. For example, if you have a backend API and a frontend web app both running in the same cluster, the frontend can reach the backend using its ClusterIP.

Key points:

• Only accessible from within the cluster
• Used for internal communication
• Not reachable from outside the cluster

You won’t use this if you need external users or systems to access your service directly.

How does NodePort work?

NodePort builds on top of ClusterIP. It exposes your Service on the same port across all nodes in your cluster. So, any traffic sent to <nodeip>:<nodeport></nodeport></nodeip> will be forwarded to your Service.

For instance, if you have three worker nodes and you set up a Service with NodePort 30080, then hitting port 30080 on any of those nodes will route traffic to your Service (and then to the appropriate Pod).

Things to know:

• Works by assigning a static port on every node
• Limited to ports in the range 30000–32767
• Good for simple setups or testing
• Doesn’t handle load balancing automatically

It’s a quick way to make something accessible externally, but not ideal for production apps where you want a clean URL or better routing.

When should you use LoadBalancer?

LoadBalancer is the type you’ll typically use in cloud environments like AWS, GCP, or Azure. It automatically provisions a cloud load balancer and assigns an external IP address to it.

Once created, traffic from the internet hits the load balancer, which then routes it to your Service inside Kubernetes.

Important notes:

• Automatically creates a NodePort and ClusterIP under the hood
• Fully managed in supported cloud providers
• Easiest way to expose a service to the public internet
• Can be expensive since each LoadBalancer Service usually costs extra in cloud billing

If you’re deploying a public-facing app and don’t want to manage additional infrastructure, LoadBalancer is often the simplest option.

So, to recap:

• Use ClusterIP for internal communication
• Use NodePort for basic external access
• Use LoadBalancer for fully external services in the cloud

Each has its place depending on what you're building and where it's running.基本上就這些。

以上是什么是Kubernetes服務，哪些類型是什么（clusterip，nodeport，loadbalancer）？的詳細內容。更多信息請關注PHP中文網其他相關文章！