# Introduction

Kubernetes is one of the services offered by the Deka GPU Service Portal, which is used to automate the deployment, management, scaling, and operation of containerized applications. Containers are a virtualization technology that allows applications to run in isolated environments while remaining resource-efficient. Kubernetes ensures container applications operate stably, scale effectively, and recover from failures. On the Kubernetes platform provided by the Deka GPU Service Portal, several advantages include:

1. #### Automated Management

   Kubernetes manages the lifecycle of containers, including deployment, scheduling, updating, and adjusting the number of pods based on application workload.
2. **Self-Healing**

   Kubernetes can automatically restart failed containers, replace them, shut down and reschedule unresponsive pods, and terminate containers that fail health checks.
3. **Load Balancing and Service Discovery**

   Kubernetes provides automatic service discovery and load balancing for applications. This ensures  network traffic is evenly distributed across all healthy pods, maintaining application availability.
4. **Rollout and Rollback Management**

   Kubernetes simplifies application updates with rolling updates and rollbacks. It allows updates to be performed without significant downtime and ensures that rollback processes can be executed quickly in case of issues to restore the application's previous state.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeySyv8MjiRtACJ9B4A5fOqdPnxSgxL3Q7SW-3DmSe5jhqM4yxyJSCOc8OEZ8liA1jb8ncREe6g44TJd3dpUCfWEGESNOoH3bReBENpeaSopXH5rH8JevQVxNYBPWClKoFeHA5W?key=STJL10WA8hk9zDcEThCoUA" alt=""><figcaption><p>Dashboard Kubernetes</p></figcaption></figure>

On the Kubernetes page, there are four menus available in the Kubernetes module:

1. **Dashboard Menu,**  this menu displays a summary of the overall status of the Kubernetes cluster. You can view general information such as the number of Pods, Deployments, Daemon Sets, and Stateful Sets that are ready to use.
2. **Workloads Menu,** this menu is used to manage and monitor the availability and scalability of applications running within the Kubernetes cluster. The Workloads page includes Pods, Deployments, DaemonSets, and StatefulSets.
3. **Services Menu,**  to make it easier for you to monitor, manage, and configure services within a Kubernetes cluster.
4. **Storages Menu,** is used to manage datastores on pods. There are two types of storage available: Persistent Volumes (PV) and Persistent Volume Claims (PVC).

After accessing the Kubernetes module, select one of the available menus (such as **Dashboard**, **Workloads**, **Services**, or **Storages**) to begin.

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

When opening the module for the first time, the page may display a message stating that the virtual cluster is unavailable. This indicates that there is no active Kubernetes cluster yet, so Kubernetes resources cannot be accessed.

To activate the cluster, make sure a Deka GPU package has been selected and the payment or top-up process has been completed. For more detailed information, please refer to the Deka GPU package selection and payment/top-up process in the [Balance ](/service-portal-ai/balance.md)module.After the process is completed successfully, wait a few minutes for the cluster to become active automatically.

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


---

# Agent Instructions: 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/deka-gpu/deka-gpu-kubernetes/introduction.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.