Edit Service Settings

Time updated：2025-12-22 09:26:17

This section describes how to edit Job settings.

Prerequisites

The Application Management for Cluster Federation extension must be installed and enabled on the KubeSphere platform.
You need to join a federated project and have the Federated Project Management permission in the corresponding workspace.

Steps

Log in to the KubeSphere web console as a user with Federated Project Management permissions and enter your federated project.
Click Application Workloads > Services in the left navigation pane.
On the right side of the service you need to operate, click , then select Edit Settings from the dropdown list.

On the Service Settings tab of the Edit Settings dialog box, modify the service settings.

For services with an internal access mode of ExternalName, you can modify the external service address.

For other services, you can modify the service’s internal access mode, workload selector, and ports.

Parameter Description

Parameter	Description
Internal Access Mode	The method for accessing the service from within the cluster. Internal Domain Name: The system does not assign a virtual IP address to the service. It can be accessed from within the cluster using a domain name in the format `<service name>.<namespace>.svc.cluster.local` or `<service name>.<namespace>`. Virtual IP Address: The system assigns a virtual IP address to the service for internal cluster access. It also supports access from within the cluster using a domain name in the format `<service name>.<namespace>.svc.cluster.local` or `<service name>.<namespace>`.
Workload Selector	Specifies the workload(s) with specific labels to which the service will forward business traffic to their managed pods. Enter label keys and values to manually set the selector. Click Add to set multiple labels. Click Specify Workload to manually select workloads. Click to the right of a created label to delete it.
Ports	Service ports and their mapping relationships with target container ports. Protocol: The protocol actually listened to by the application in the target container. To use the application governance features provided by KubeSphere, ensure the protocol selected here matches the one actually listened to by the application in the target container. Name: The name of the service port. KubeSphere’s application governance features require service port names to be prefixed with the lowercase protocol name. To use the application governance features provided by KubeSphere, use the lowercase protocol name as the prefix for the port name (e.g., http-). Container Port: The port number actually listened to by the application in the target container. Service Port: The port number of the service. Click Add to set multiple service ports. Click to the right of a created service port to delete it.

Internal Access Mode

The method for accessing the service from within the cluster.

Internal Domain Name: The system does not assign a virtual IP address to the service. It can be accessed from within the cluster using a domain name in the format <service name>.<namespace>.svc.cluster.local or <service name>.<namespace>.
Virtual IP Address: The system assigns a virtual IP address to the service for internal cluster access. It also supports access from within the cluster using a domain name in the format <service name>.<namespace>.svc.cluster.local or <service name>.<namespace>.

Workload Selector

Specifies the workload(s) with specific labels to which the service will forward business traffic to their managed pods.

Enter label keys and values to manually set the selector. Click Add to set multiple labels.
Click Specify Workload to manually select workloads.
Click to the right of a created label to delete it.

Ports

Service ports and their mapping relationships with target container ports.

Protocol: The protocol actually listened to by the application in the target container. To use the application governance features provided by KubeSphere, ensure the protocol selected here matches the one actually listened to by the application in the target container.
Name: The name of the service port. KubeSphere’s application governance features require service port names to be prefixed with the lowercase protocol name. To use the application governance features provided by KubeSphere, use the lowercase protocol name as the prefix for the port name (e.g., http-).
Container Port: The port number actually listened to by the application in the target container.
Service Port: The port number of the service.

Click Add to set multiple service ports. Click to the right of a created service port to delete it.

On the Cluster Differential Settings tab of the Edit Settings dialog box, configure differential settings for the service in different clusters based on ports, then click OK.