Edit Service Settings

This section explains how to edit service settings.

Prerequisites

Application Management for Cluster Federation should have been installed and enabled.
You should join a multi-cluster project and have the Federated Project Management permission within the project.

Steps

Log in to the KubeSphere web console with a user who has the Federated Project Management permission, and access your multi-cluster project.
Click Application Workloads > Services in the left navigation pane.
Click on the right side of the service you want to operate, then select Edit Settings from the dropdown list.

On the Service Settings tab, modify the service settings.

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

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

Parameter Description

Parameter	Description
Internal Access Mode	The way to access the service within the cluster. Internal Domain Name: The system does not assign a virtual IP address to the service. It can be accessed internally by using 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 access within the cluster. It also supports access internally by using the format `<service name>.<namespace>.svc.cluster.local` or `<service name>.<namespace>`.
Workload Selector	Specify the workloads with specific labels to which the service routes business traffic. Manually set selectors by entering the key and value of a label. Click Add to set multiple labels. Manually select workloads by clicking Specify Workload. Click on the right side of a created label to delete it.
Ports	Map service ports and their corresponding container ports. Protocol: The protocol that the application in the target container actually listens on. To use the application governance features provided by KubeSphere, ensure that the protocol selected here matches the one the application in the target container actually listens on. Name: The name of the service port. The application governance features of KubeSphere require the service port name to have the protocol name in lowercase as a prefix. 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 on which the application in the target container actually listens. Service Port: The port number of the service. Click Add to set multiple service ports. Click on the right side of a created service port to delete it.

Internal Access Mode

The way to access the service within the cluster.

Internal Domain Name: The system does not assign a virtual IP address to the service. It can be accessed internally by using 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 access within the cluster. It also supports access internally by using the format <service name>.<namespace>.svc.cluster.local or <service name>.<namespace>.

Workload Selector

Specify the workloads with specific labels to which the service routes business traffic.

Manually set selectors by entering the key and value of a label. Click Add to set multiple labels.
Manually select workloads by clicking Specify Workload.
Click on the right side of a created label to delete it.

Ports

Map service ports and their corresponding container ports.

Protocol: The protocol that the application in the target container actually listens on. To use the application governance features provided by KubeSphere, ensure that the protocol selected here matches the one the application in the target container actually listens on.
Name: The name of the service port. The application governance features of KubeSphere require the service port name to have the protocol name in lowercase as a prefix. 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 on which the application in the target container actually listens.
Service Port: The port number of the service.

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

On the Cluster Differences tab, differentiate the service based on ports in different clusters, then click OK.

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 : Edit Service Information Next : Edit Service External Access Settings

What’s on this Page