# service

The describe service command retrieves detailed information about a specific Service in the Kubernetes cluster. This includes metadata, service type, selector labels, exposed ports, target endpoints, and load balancing details.

## Usage

```
cldkctl describe service [name] [flags]
```

## Steps

Follow the steps below to run and view the result of this command:

1. Run the following command in your terminal:

```
cldkctl describe service [name]
```

2. Replace `[name]` with the Service name you want to inspect.
3. To view the resource name, refer to the corresponding get service section.
4. If the resource is located in a non-default namespace, include the `-n` or `--namespace` flag followed by the namespace name.

```
cldkctl describe [resource] [name] -n [namespace]
```

5. Once completed successfully, the detailed information about the specified Service will appear in your terminal. The output includes metadata, type, selector labels, port configuration, and cluster IP details.

<figure><img src="/files/kyHZSD1rT2Slfzx7WmdN" alt=""><figcaption></figcaption></figure>

The following table describes the additional fields specific to the Service resource.

| Column                     | Description                                                                       |
| -------------------------- | --------------------------------------------------------------------------------- |
| metadata.name              | The name of the Service.                                                          |
| metadata.namespace         | The namespace where the Service is deployed.                                      |
| spec.type                  | The type of Service.                                                              |
| spec.selector              | Defines the label selector used to match pods that the Service routes traffic to. |
| spec.ports                 | Lists the exposed ports for the Service, including port and target port mapping.  |
| spec.ports.name            | The logical name assigned to the port.                                            |
| spec.ports.port            | The port number exposed by the Service.                                           |
| spec.ports.targetPort      | The port number on the pod targeted by the Service.                               |
| spec.ports.protocol        | The network protocol used by the Service.                                         |
| spec.clusterIP             | The internal IP address assigned to the Service within the cluster.               |
| spec.clusterIPs            | A list of cluster IPs associated with the Service.                                |
| spec.sessionAffinity       | Defines how traffic from the same client is routed to the same pod                |
| spec.ipFamilies            | Indicates the IP address families supported by the Service                        |
| spec.ipFamilyPolicy        | Specifies how dual-stack Service IP families are assigned.                        |
| spec.internalTrafficPolicy | Determines how internal cluster traffic is routed.                                |
| status.loadBalancer        | Provides information about the external load balancer if applicable.              |

## Flags

{% hint style="info" %}

1. This command supports [global flags.](/guidance-for-individual/cloudeka-api-list/global-flags.md) Refer to the Global Flags section for details.
2. For common metadata fields, refer to the Common Output Fields table at the beginning of this section.
   {% endhint %}

| Flag       | Description                        |
| ---------- | ---------------------------------- |
| -h, --help | Help for describe service command. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudeka.ai/guidance-for-individual/cloudeka-api-list/command-reference/cldkctl-describe/service.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.