< img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=3131724&fmt=gif" />
🚀 KubeSphere v4.1.2 with Enhancements and Bug Fixes is available now. Read the release notes for v4.1.2 → close
  • English
    • English
    • 简体中文
    1. 1.Create a KubeSphere Cloud account and log in to the platform.
    2. 2.In the upper-right corner, click Console, and then click Lite Cluster on the left.
    3. 3.Create a K8s cluster with KubeSphere installed.
    4. 4.Access KubeSphere with the default account and password (admin/P@88w0rd).
  •  Star
  1. Docs / 
  2. Documentation / 
  3. Cluster Management / 
  4. Application Workloads / 
  5. Services / 
  6. View Service Details

Documentation

Last updated:
    Edit

    View Service Details

    This section explains how to view the service details.

    Prerequisites

    You should join a cluster and have the Application Workload Viewing permission within the cluster. For more information, refer to "Cluster Members" and "Cluster Roles".

    Steps

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

    2. Click Application Workloads > Services in the left navigation pane.

    3. Click the name of a service in the list to open its details page.

    4. In the Attributes section on the left side of the service details page, view the resource attributes of the service.

      Parameter Description

      Cluster

      The cluster to which the service belongs.

      Project

      The project to which the service belongs.

      Type

      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.

      App

      The name of the application to which the service belongs. You can create an application that includes multiple services, with each service corresponding to a workload.

      Virtual IP Address

      The virtual IP address for internal access within the cluster. Displayed only for services with the VirtualIP type.

      External IP Address

      The IP address for external access outside the cluster. Displayed only when external access is enabled for the service.

      Session Affinity

      Whether session affinity is enabled:

      • Enabled: Session affinity is enabled. If the service has multiple pods, requests from the same client IP address within a certain period (default is 10800 seconds) will be forwarded to the same pod.

      • Disabled: Session affinity is not enabled. If the service has multiple pods, requests from the same client IP address will be randomly forwarded to different pods.

      Selector

      The selector for the service’s pods. The pod selector consists of one or more pod labels, and the service will route client requests to pods that have all the specified labels.

      DNS

      The internal domain of the service within the cluster, accessible within the cluster.

      Endpoint

      The virtual IP address and container port of the target pods for the service.

      Creation Time

      The creation time of the service.

      Creator

      The user who created the service.

    5. In the Resource Status tab on the right side of the service details page, view the container ports, workloads, and pods for the service.

      Parameter Description

      Ports

      To enable containers to be accessed properly, KubeSphere defines the following types of ports:

      • Container Port: The port on which the application in the container listens, only accessible within the pod.

      • Service Port: The port for the virtual IP address of the service, only accessible within the cluster. Requests sent to the service port will be forwarded to the container port.

      • Node Port: The port on the node host, accessible from outside the cluster. Requests sent to the node port will be forwarded to the service port. Services with the NodePort or LoadBalancer type have node ports.

      Workloads

      Displays the name, update time, type, status, and current revision records of the workload managing the pods.

      Pods

      • Click chevron-down to view information about the containers running in the pod.

      • Click the name of the pod to view container details.

      • Enter keywords in the search box above the pod list to search for pods whose names contain specific keywords.

      • Click Refresh in the upper-right corner of the pod list to refresh the information.

    6. Click the Metadata tab on the right side of the service details page to view the labels and annotations for the service.

    7. Click the Events tab on the right side of the service details page to view events related to the service.

      Parameter Description

      Type

      The type of the event, including Normal and Warning.

      Reason

      The reason for the event.

      Occurred

      The time when the event occurred.

      Source

      The component that reported the event.

      Message

      The content of the event message.

    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 : View Service List
    What’s on this Page