Help Center/ Ubiquitous Cloud Native Service/ User Guide/ UCS Clusters/ Single-Cluster Management/ Networking/ Services
Updated on 2024-06-17 GMT+08:00
View PDF
Share

Services

Services provide fixed modes for accessing workloads in a cluster. You can create the following Services on the cluster console:

  • ClusterIP

    A workload can be accessed from other workloads in the same cluster through a cluster-internal domain name. A cluster-internal domain name is in the format of <User-defined Service name>.<Namespace of the workload>.svc.cluster.local, for example, nginx.default.svc.cluster.local.

  • NodePort

    A workload can be accessed from outside the cluster. A NodePort Service is exposed on each node's IP address at a static port. If a node in the cluster is bound to an elastic IP address (EIP), you can use <EIP>:<NodePort> to access the workload from a public network.

  • LoadBalancer

    A workload can be accessed from a public network through a load balancer. This access type is applicable to Services that need to be exposed to a public network in the system. The access address is in the format of <IP address of public network load balancer>:<access port>, for example, 10.117.117.117:80.

ClusterIP

  1. Access the cluster console.
  2. In the navigation pane, choose Services & Ingresses. On the displayed page, click the Services tab and select the namespace that the Service belongs to. For details about how to create a namespace, see Creating a Namespace.
  3. Click Create Service in the upper right corner and configure the parameters.

    • Service Name: Can be the same as the workload name.
    • Service Type: Select ClusterIP.
    • Namespace: Set it to the namespace that the workload belongs to.
    • Selector: Add a label and click Add. A Service selects a pod based on the added label. You can also click Reference Workload Label to reference the label of an existing workload. In the dialog box that is displayed, select a workload and click OK.
    • Port
      • Protocol: Select a protocol used by the Service.
      • Service Port: Port mapped to the container port at the cluster-internal IP address. The workload can be accessed at <cluster-internal IP address>:<access port>. The port number range is 1–65535.
      • Container Port: Port on which the workload listens. For example, the Nginx application listens on port 80 (container port).

  4. Click OK.

NodePort

  1. Access the cluster console.
  2. In the navigation pane, choose Services & Ingresses. On the displayed page, click the Services tab and select the namespace that the Service belongs to. For details about how to create a namespace, see Creating a Namespace.
  3. Click Create Service in the upper right corner and configure the parameters.

    • Service Name: Can be the same as the workload name.
    • Service Type: Select NodePort.
    • Service Affinity
      • Cluster-level: The IP addresses and access ports of all nodes in a cluster can be used to access the workloads associated with the Service. However, performance loss is introduced due to hops, and source IP addresses cannot be obtained.
      • Node-level: Only the IP address and access port of the node where the workload is located can be used to access the workload associated with the Service. Service access will not cause performance loss due to route redirection, and the source IP address of the client can be obtained.
    • Namespace: Set it to the namespace that the workload belongs to.
    • Selector: Add a label and click Add. A Service selects a pod based on the added label. You can also click Reference Workload Label to reference the label of an existing workload. In the dialog box that is displayed, select a workload and click OK.
    • Port
      • Protocol: Select a protocol used by the Service.
      • Service Port: Port mapped to the container port at the cluster-internal IP address. The application can be accessed at <cluster-internal IP address>:<access port>. The port number range is 1–65535.
      • Container Port: Port on which the workload listens, defined in the container image. For example, the Nginx application listens on port 80 (container port).
      • Node Port: Port to which the container port will be mapped when the node private IP address is used for accessing the application. The port number range is 30000–32767. You are advised to select Auto.
        • Auto: The system automatically assigns a port number.
        • Custom: Specify a fixed node port. The port number range is 30000–32767. Ensure that the port is unique in a cluster.

  4. Click OK.

LoadBalancer

  1. Access the cluster console.
  2. In the navigation pane, choose Services & Ingresses. On the displayed page, click the Services tab and select the namespace that the Service belongs to. For details about how to create a namespace, see Creating a Namespace.
  3. Click Create Service in the upper right corner and configure the parameters.

    • Service Name: Can be the same as the workload name.
    • Service Type: Select LoadBalancer.
    • Service Affinity
      • Cluster-level: The IP addresses and access ports of all nodes in a cluster can be used to access the workloads associated with the Service. However, performance loss is introduced due to hops, and source IP addresses cannot be obtained.
      • Node-level: Only the IP address and access port of the node where the workload is located can be used to access the workload associated with the Service. Service access will not cause performance loss due to route redirection, and the source IP address of the client can be obtained.
    • Namespace: Set it to the namespace that the workload belongs to.
    • Selector: Add a label and click Add. A Service selects a pod based on the added label. You can also click Reference Workload Label to reference the label of an existing workload. In the dialog box that is displayed, select a workload and click OK.
    • Port
      • Protocol: Select a protocol used by the Service.
      • Service Port: Port mapped to the container port at the cluster-internal IP address. The application can be accessed at <cluster-internal IP address>:<access port>. The port number range is 1–65535.
      • Container Port: Port on which the workload listens, defined in the container image. For example, the Nginx application listens on port 80 (container port).
    • Annotation: The key-value pair format is supported. Configure annotations based on your service and vendor requirements and then click Add.

  4. Click OK.
Parent topic: Networking