View Service List

This section explains how to view the service list.

Steps

Log in to the KubeSphere web console with a user who has the Application Workload Viewing permission, and access your project.

Click Application Workloads > Services in the left navigation pane.

The service list provides the following information:

Parameter Description

Parameter	Description
Name	The name and description of the service.
Service Type	The type of service. Depending on how the service was created, KubeSphere categorizes services into the following types: Stateful Service: The internal access mode of the service is Headless, and the backend workload is Statefulset. Stateless Service: The internal access mode of the service is VirtualIP, and the backend workload is Deployment. External Service: Services forward business traffic to other services outside the cluster. The system does not allocate virtual IP addresses for services. They can be accessed internally within the cluster using the domain name format `<service name>.<project name>.svc.cluster.local`. Custom Service: Services created by users with custom internal access modes and backend workloads.
App	The application to which the service belongs.
Internal Access	The internal access mode for the service. Headless: The system does not assign a virtual IP address to the service. It can be accessed internally by using the format `<service name>.<project name>.svc.cluster.local` or `<service name>.<project name>`. VirtualIP: The system assigns a virtual IP address to the service for internal access within the cluster. It also supports access internally by using the format `<service name>.<project name>.svc.cluster.local` or `<service name>.<project name>`. ExternalName: The service routes business traffic to other services outside the cluster. The system does not assign a virtual IP address to the service, and it can be accessed internally by using the format `<service name>.<project name>.svc.cluster.local`.
External Access	The external access mode for the service. NodePort: The system maps the ports of nodes to the service ports, and the service can be accessed through the node IP address and node port. LoadBalancer: On the basis of a NodePort service, the system assigns an external IP address to the service and binds the external IP address to an external load balancer. The external load balancer listens on the node port corresponding to the service, allowing access to the service through the external IP address. To achieve this, LoadBalancer-type services need support from load balancer plugins and the infrastructure environment, and relevant annotations need to be set. For more information, please contact your infrastructure environment provider.
Creation Time	The time the service created.

Name

The name and description of the service.

Service Type

The type of service. Depending on how the service was created, KubeSphere categorizes services into the following types:

Stateful Service: The internal access mode of the service is Headless, and the backend workload is Statefulset.
Stateless Service: The internal access mode of the service is VirtualIP, and the backend workload is Deployment.
- External Service: Services forward business traffic to other services outside the cluster. The system does not allocate virtual IP addresses for services. They can be accessed internally within the cluster using the domain name format <service name>.<project name>.svc.cluster.local.
- Custom Service: Services created by users with custom internal access modes and backend workloads.

App

The application to which the service belongs.

Internal Access

The internal access mode for the service.

Headless: The system does not assign a virtual IP address to the service. It can be accessed internally by using the format <service name>.<project name>.svc.cluster.local or <service name>.<project name>.
VirtualIP: The system assigns a virtual IP address to the service for internal access within the cluster. It also supports access internally by using the format <service name>.<project name>.svc.cluster.local or <service name>.<project name>.
ExternalName: The service routes business traffic to other services outside the cluster. The system does not assign a virtual IP address to the service, and it can be accessed internally by using the format <service name>.<project name>.svc.cluster.local.

External Access

The external access mode for the service.

NodePort: The system maps the ports of nodes to the service ports, and the service can be accessed through the node IP address and node port.
LoadBalancer: On the basis of a NodePort service, the system assigns an external IP address to the service and binds the external IP address to an external load balancer. The external load balancer listens on the node port corresponding to the service, allowing access to the service through the external IP address. To achieve this, LoadBalancer-type services need support from load balancer plugins and the infrastructure environment, and relevant annotations need to be set. For more information, please contact your infrastructure environment provider.

Creation Time

The time the service created.

Click the search box at the top of the list to search for services by name.

Click in the upper right corner of the list to refresh the list information.

Click in the upper right corner of the list to customize the information displayed in the list.

Feedback

Was this page Helpful?

Receive the latest news, articles and updates from KubeSphere

Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.

Previous : Create Services Using Existing Workloads Next : View Service Details

What’s on this Page