kop-cli 0.1.0a7__tar.gz → 0.2.0__tar.gz

{kop_cli-0.1.0a7 → kop_cli-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: kop-cli
-Version: 0.1.0a7
+Version: 0.2.0
 Summary: Terminal-based kubernetes operation platform
 Author-email: vegaoqiang <vegaoqiang@gmail.com>
 License-Expression: Apache-2.0
@@ -26,10 +26,12 @@ Classifier: Topic :: Software Development
 Classifier: Topic :: System :: Systems Administration
 Classifier: Topic :: Terminals
 Requires-Python: >=3.9
-Requires-Dist: kubernetes>=33.1.0
+Requires-Dist: kubernetes==33.1.0
 Requires-Dist: pyte
-Requires-Dist: textual>=8.1.1
-Requires-Dist: textual[syntax]
+Requires-Dist: textual==8.2.7
+Requires-Dist: tree-sitter-bash
+Requires-Dist: tree-sitter-json
+Requires-Dist: tree-sitter-yaml
 Provides-Extra: dev
 Requires-Dist: pytest-asyncio; extra == 'dev'
 Requires-Dist: pytest>=9.0.2; extra == 'dev'
@@ -47,23 +49,43 @@ Description-Content-Type: text/markdown
 `kop` is a terminal-based (TUI) Kubernetes operations platform. Its goal is to provide an interactive experience similar to desktop cluster management tools, but fully within the terminal command line, aiming to solve the problem of conveniently operating Kubernetes clusters when no desktop environment is available.
 
 
-## Requirements
+## Installation
+Here's how to install kop.
 
-- Python `>=3.9`
-- Terminal environment with TUI support (TrueColor/xterm-256color/Mouse Tracking)
+### Install from PyPI
 
-## Installation
+You can install kop via PyPI with the following command:
 
-```bash
+```shell
 pip install kop-cli
 ```
 
-After installation, you can directly run:
-
-```bash
+After installation, you can run:
+```shell
 kop --version
 ```
 
+### Install from an offline binary package
+
+If the target machine cannot access PyPI, download the offline binary package from the [GitHub Releases](https://github.com/vegaoqiang/kop/releases) page on another machine first.
+
+1. Open the release version you want to install.
+2. Download the binary package that matches your operating system and CPU architecture.
+3. Copy the package to the target machine.
+4. Extract the package and run the `kop` binary.
+
+On Linux or macOS, you may need to grant execute permission before running it:
+
+```shell
+chmod +x kop
+./kop --version
+```
+
+On Windows, run `kop.exe` from PowerShell or Command Prompt:
+
+```powershell
+.\kop.exe --version
+```
 
 ## Usage
 
@@ -90,30 +112,10 @@ In this mode, the file path and kubeconfig validity are verified, and after vali
 
 ## Operations and Shortcuts
 See demo video:
-[![Watch the demo](https://img.youtube.com/vi/sEXl9UQQxVc/maxresdefault.jpg)](https://www.youtube.com/watch?v=sEXl9UQQxVc)
+[![Watch the demo](https://img.youtube.com/vi/6L1jOtYvKYg/maxresdefault.jpg)](https://www.youtube.com/watch?v=6L1jOtYvKYg)
 
 Please refer to the [Documentation](https://vegaoqiang.github.io/kop/) for more detailed usage instructions.
 
-### Startup Page (Cluster List)
-
-- `a`: Add cluster
-- `c` / `Enter`: Connect to cluster
-- `d`: Delete cluster
-- `e`: Edit cluster
-- `s`: Sync local kubeconfig
-- Arrow keys `↑↓←→`: Move between cluster cards
-
-### Resource Page
-
-- Select resource type from the left-side menu
-- `]`: Quickly focus the namespace selector
-- `/`: Search (menu or resources)
-- `c`: Create resource (when supported by the current resource type)
-- `Esc`: Return to cluster home page
-
-Tip: Available actions differ by resource in the details/operation panel. The bottom of the interface shows available key hints.
-
-
 ## FAQ
 
 ### Mouse click not working

{kop_cli-0.1.0a7 → kop_cli-0.2.0}/README.md

@@ -9,23 +9,43 @@
 `kop` is a terminal-based (TUI) Kubernetes operations platform. Its goal is to provide an interactive experience similar to desktop cluster management tools, but fully within the terminal command line, aiming to solve the problem of conveniently operating Kubernetes clusters when no desktop environment is available.
 
 
-## Requirements
+## Installation
+Here's how to install kop.
 
-- Python `>=3.9`
-- Terminal environment with TUI support (TrueColor/xterm-256color/Mouse Tracking)
+### Install from PyPI
 
-## Installation
+You can install kop via PyPI with the following command:
 
-```bash
+```shell
 pip install kop-cli
 ```
 
-After installation, you can directly run:
-
-```bash
+After installation, you can run:
+```shell
 kop --version
 ```
 
+### Install from an offline binary package
+
+If the target machine cannot access PyPI, download the offline binary package from the [GitHub Releases](https://github.com/vegaoqiang/kop/releases) page on another machine first.
+
+1. Open the release version you want to install.
+2. Download the binary package that matches your operating system and CPU architecture.
+3. Copy the package to the target machine.
+4. Extract the package and run the `kop` binary.
+
+On Linux or macOS, you may need to grant execute permission before running it:
+
+```shell
+chmod +x kop
+./kop --version
+```
+
+On Windows, run `kop.exe` from PowerShell or Command Prompt:
+
+```powershell
+.\kop.exe --version
+```
 
 ## Usage
 
@@ -52,30 +72,10 @@ In this mode, the file path and kubeconfig validity are verified, and after vali
 
 ## Operations and Shortcuts
 See demo video:
-[![Watch the demo](https://img.youtube.com/vi/sEXl9UQQxVc/maxresdefault.jpg)](https://www.youtube.com/watch?v=sEXl9UQQxVc)
+[![Watch the demo](https://img.youtube.com/vi/6L1jOtYvKYg/maxresdefault.jpg)](https://www.youtube.com/watch?v=6L1jOtYvKYg)
 
 Please refer to the [Documentation](https://vegaoqiang.github.io/kop/) for more detailed usage instructions.
 
-### Startup Page (Cluster List)
-
-- `a`: Add cluster
-- `c` / `Enter`: Connect to cluster
-- `d`: Delete cluster
-- `e`: Edit cluster
-- `s`: Sync local kubeconfig
-- Arrow keys `↑↓←→`: Move between cluster cards
-
-### Resource Page
-
-- Select resource type from the left-side menu
-- `]`: Quickly focus the namespace selector
-- `/`: Search (menu or resources)
-- `c`: Create resource (when supported by the current resource type)
-- `Esc`: Return to cluster home page
-
-Tip: Available actions differ by resource in the details/operation panel. The bottom of the interface shows available key hints.
-
-
 ## FAQ
 
 ### Mouse click not working

kop_cli-0.2.0/docs/faq.md

@@ -0,0 +1,45 @@
+---
+hide:
+  - navigation
+---
+
+# FAQ
+
+## Mouse click not working
+
+When using iTerm2 on macOS to SSH into a remote host and run kop, mouse clicks may not work. This happens because in Linux environments, most command-line programs rely on the `$TERM` variable to determine terminal capabilities (such as colors and bold text). A common value is `xterm-256color`. While `xterm-256color` is a general standard, it does not cover all extensions of modern terminals (such as advanced mouse protocols or synchronized updates). `Textual` is a very advanced TUI (text user interface) framework. To provide the best experience, it tries to detect which terminal is actually running. For `iTerm2`, it supports many non-standard advanced features. Textual has internal optimization logic: when it detects `TERM_PROGRAM=iTerm.app`, it switches to an interaction mode optimized for `iTerm2`. If Textual does not see `TERM_PROGRAM=iTerm.app`, it may avoid enabling some advanced interaction features, or due to configuration conflicts, it may fail to properly fall back to a generic mouse mode.
+
+Solutions:
+
+1. Manually run `export TERM_PROGRAM=iTerm.app` on the remote host. After restarting `kop`, mouse clicks should work normally.
+2. Update local SSH config on macOS: `~/.ssh/config`, add:
+
+```shell
+Host *
+    SendEnv TERM_PROGRAM
+```
+
+Update remote host `sshd` config: `/etc/ssh/sshd_config`, add:
+
+```shell
+AcceptEnv TERM_PROGRAM
+```
+
+After restarting the `sshd` service, disconnect and reconnect to the remote host, then run `kop` again. Mouse clicking should be restored.
+
+
+## Why doesn't kop look good on macOS?
+kop is built with Textual for terminal UI. Please refer to the Textual FAQ section about display issues in the default macOS terminal for fixes: https://textual.textualize.io/FAQ/#why-doesnt-textual-look-good-on-macos
+
+## Abnormal display on Linux console
+
+You may use kop on Linux console (a monitor connected to a server via a VGA cable) and find kop UI rendering issues or even crashes. This is because Linux kernel built-in virtual terminals (`tty1`~`tty6`):
+
+* ❌ Do not support True Color (24-bit)
+* ❌ Do not support 256 colors
+* ✅ Only support 16 colors (sometimes even only 8)
+* ✅ Rendering is controlled by the kernel (not by a terminal emulator)
+
+There is currently no good solution. If you must use kop on a physical terminal, one compromise is `kmscon`.
+
+Kmscon is a simple terminal emulator based on linux kernel mode setting (KMS). It is an attempt to replace the in-kernel VT implementation with a userspace console. See https://github.com/kmscon/kmscon

{kop_cli-0.1.0a7 → kop_cli-0.2.0}/docs/getting_started.md

@@ -1,3 +1,8 @@
+---
+hide:
+  - navigation
+---
+
 # Getting started
 
 ## Requirements
@@ -23,7 +28,9 @@ The new [Windows Terminal](https://apps.microsoft.com/store/detail/windows-termi
 ## Installation
 Here's how to install kop.
 
-You can install kop via PyPI, with the following command:
+### Install from PyPI
+
+You can install kop via PyPI with the following command:
 
 ```shell
 pip install kop-cli
@@ -34,6 +41,28 @@ After installation, you can run:
 kop --version
 ```
 
+### Install from an offline binary package
+
+If the target machine cannot access PyPI, download the offline binary package from the [GitHub Releases](https://github.com/vegaoqiang/kop/releases) page on another machine first.
+
+1. Open the release version you want to install.
+2. Download the binary package that matches your operating system and CPU architecture.
+3. Copy the package to the target machine.
+4. Extract the package and run the `kop` binary.
+
+On Linux or macOS, you may need to grant execute permission before running it:
+
+```shell
+chmod +x kop
+./kop --version
+```
+
+On Windows, run `kop.exe` from PowerShell or Command Prompt:
+
+```powershell
+.\kop.exe --version
+```
+
 ## Usage
 
 ### 1. Startup

kop_cli-0.2.0/docs/guide/ClusterRoleBindings.md

@@ -0,0 +1,48 @@
+# Cluster Role Bindings
+This document explains how to operate Cluster Role Bindings through kop.
+
+## Binding keys
+Available shortcuts for ClusterRoleBinding-related operations are shown in the Footer area at the bottom of the page. Available actions may vary slightly by context; always use the real-time prompts in the Footer as the source of truth.
+
+| Key | Action |
+| --- | --- |
+| `d` | Delete ClusterRoleBinding |
+| `e` | Edit ClusterRoleBinding |
+| `n` | Next Page |
+| `p` | Previous Page |
+
+> Some `keys` are shown in the Footer only under specific conditions. For example, `n` and `p` are displayed only when the total number of resources exceeds the current screen height.
+
+## Actions
+The following sections describe what each action does and how to use it.
+
+### Edit ClusterRoleBinding
+Edits the ClusterRoleBinding YAML configuration and submits changes.
+
+**Steps:**
+
+1. In the left resource navigator, go to `Cluster Role Bindings`.
+2. Select the target ClusterRoleBinding in the list.
+3. Press `e` to open the YAML editor view.
+4. Modify the content and save to submit.
+
+**Notes:**
+
+- Invalid or immutable field changes are rejected by the Kubernetes API.
+- If an update fails, adjust based on the error message and retry.
+- `Edit ClusterRoleBinding` opens in the `Action Workspace`. See [Action Workspace](../tutorial.md#action-workspace) for details.
+
+### Delete ClusterRoleBinding
+Deletes the currently selected ClusterRoleBinding resource.
+
+**Steps:**
+
+1. Select the target ClusterRoleBinding in the `Cluster Role Bindings` list.
+2. Press `d` to trigger deletion.
+3. Confirm the action in the prompt.
+
+**Notes:**
+
+- Deletion removes the selected ClusterRoleBinding object from the cluster.
+- Check dependent workloads before deletion to avoid service impact.
+

kop_cli-0.2.0/docs/guide/ClusterRoles.md

@@ -0,0 +1,48 @@
+# Cluster Roles
+This document explains how to operate Cluster Roles through kop.
+
+## Binding keys
+Available shortcuts for ClusterRole-related operations are shown in the Footer area at the bottom of the page. Available actions may vary slightly by context; always use the real-time prompts in the Footer as the source of truth.
+
+| Key | Action |
+| --- | --- |
+| `d` | Delete ClusterRole |
+| `e` | Edit ClusterRole |
+| `n` | Next Page |
+| `p` | Previous Page |
+
+> Some `keys` are shown in the Footer only under specific conditions. For example, `n` and `p` are displayed only when the total number of resources exceeds the current screen height.
+
+## Actions
+The following sections describe what each action does and how to use it.
+
+### Edit ClusterRole
+Edits the ClusterRole YAML configuration and submits changes.
+
+**Steps:**
+
+1. In the left resource navigator, go to `Cluster Roles`.
+2. Select the target ClusterRole in the list.
+3. Press `e` to open the YAML editor view.
+4. Modify the content and save to submit.
+
+**Notes:**
+
+- Invalid or immutable field changes are rejected by the Kubernetes API.
+- If an update fails, adjust based on the error message and retry.
+- `Edit ClusterRole` opens in the `Action Workspace`. See [Action Workspace](../tutorial.md#action-workspace) for details.
+
+### Delete ClusterRole
+Deletes the currently selected ClusterRole resource.
+
+**Steps:**
+
+1. Select the target ClusterRole in the `Cluster Roles` list.
+2. Press `d` to trigger deletion.
+3. Confirm the action in the prompt.
+
+**Notes:**
+
+- Deletion removes the selected ClusterRole object from the cluster.
+- Check dependent workloads before deletion to avoid service impact.
+

kop_cli-0.1.0a7/docs/tutorial.md → kop_cli-0.2.0/docs/guide/Clusters.md

@@ -1,6 +1,7 @@
-# Tutorial
+# Clusters
+kop support manage multiple kubernetes clusters, the documents show how to add or sync kubernetes cluster to kop
 
-## Add Kubernetes CLuster
+## Add Kubernetes Cluster
 
 After starting kop, it reads the ~/.kube/config file by default.
 
@@ -9,11 +10,11 @@ After starting kop, it reads the ~/.kube/config file by default.
 
 If the host running kop does not have Kubernetes (connecting to a remote Kubernetes cluster over the network). After starting kop, you will see relevant prompts.
 
-![startup_without_cluster](images/tutorial/startup_without_cluster.png)
+![startup_without_cluster](../images/tutorial/startup_without_cluster.png)
 
 At this point, you can open the `Add Cluster` view by clicking the `[Add]` button with the mouse or pressing `a` on the keyboard.
 
-![add_new_cluster](images/tutorial/add_new_cluster.png)
+![add_new_cluster](../images/tutorial/add_new_cluster.png)
 
 Then paste the contents of your kubeconfig file into the `Paste Your Cluster Config` area. Then paste the contents of your kubeconfig file into the content area, and then click the `[Save]` button or press `'ctrl+s'` to save.
 

kop_cli-0.2.0/docs/guide/ConfigMaps.md

@@ -0,0 +1,48 @@
+# ConfigMaps
+This document explains how to operate ConfigMaps through kop.
+
+## Binding keys
+Available shortcuts for ConfigMap-related operations are shown in the Footer area at the bottom of the page. Available actions may vary slightly by context; always use the real-time prompts in the Footer as the source of truth.
+
+| Key | Action |
+| --- | --- |
+| `d` | Delete ConfigMap |
+| `e` | Edit ConfigMap |
+| `n` | Next Page |
+| `p` | Previous Page |
+
+> Some `keys` are shown in the Footer only under specific conditions. For example, `n` and `p` are displayed only when the total number of resources exceeds the current screen height.
+
+## Actions
+The following sections describe what each action does and how to use it.
+
+### Edit ConfigMap
+Edits the ConfigMap YAML configuration and submits changes.
+
+**Steps:**
+
+1. In the left resource navigator, go to `ConfigMaps`.
+2. Select the target ConfigMap in the list.
+3. Press `e` to open the YAML editor view.
+4. Modify the content and save to submit.
+
+**Notes:**
+
+- Invalid or immutable field changes are rejected by the Kubernetes API.
+- If an update fails, adjust based on the error message and retry.
+- `Edit ConfigMap` opens in the `Action Workspace`. See [Action Workspace](../tutorial.md#action-workspace) for details.
+
+### Delete ConfigMap
+Deletes the currently selected ConfigMap resource.
+
+**Steps:**
+
+1. Select the target ConfigMap in the `ConfigMaps` list.
+2. Press `d` to trigger deletion.
+3. Confirm the action in the prompt.
+
+**Notes:**
+
+- Deletion removes the selected ConfigMap object from the cluster.
+- Check dependent workloads before deletion to avoid service impact.
+

kop_cli-0.2.0/docs/guide/CronJobs.md

@@ -0,0 +1,81 @@
+# CronJobs
+This document explains how to operate CronJobs through kop.
+
+## Binding keys
+Available shortcuts for CronJob-related operations are shown in the Footer area at the bottom of the page. Available actions may vary slightly by context; always use the real-time prompts in the Footer as the source of truth.
+
+| Key | Action |
+| --- | --- |
+| `d` | Delete CronJob |
+| `e` | Edit CronJob |
+| `s` | Suspend/Resume CronJob |
+| `t` | Trigger CronJob |
+| `n` | Next Page |
+| `p` | Previous Page |
+
+> Some `keys` are shown in the Footer only under specific conditions. For example, `n` and `p` are displayed only when the total number of resources exceeds the current screen height.
+
+## Actions
+The following sections describe what each action does and how to use it.
+
+### Trigger CronJob
+Creates a one-off Job immediately from the selected CronJob.
+
+**Steps:**
+
+1. In the left resource navigator, go to `CronJobs`.
+2. Select the target CronJob in the list.
+3. Press `t` to trigger a one-off run.
+4. Confirm the action in the prompt.
+5. Verify the new Job appears in related resources.
+
+**Notes:**
+
+- Trigger does not change the regular schedule.
+- Use this action to validate the job template on demand.
+
+### Suspend/Resume CronJob
+Suspends or resumes scheduling for the selected CronJob.
+
+**Steps:**
+
+1. Select the target CronJob in the `CronJobs` list.
+2. Press `s` to toggle scheduling state.
+3. Confirm the action in the prompt.
+4. Check the updated state in the resource table or detail view.
+
+**Notes:**
+
+- Suspend stops future schedule triggers but does not cancel already started Jobs.
+- Resume re-enables schedule-based execution.
+
+### Edit CronJob
+Edits the CronJob YAML configuration and submits changes.
+
+**Steps:**
+
+1. In the left resource navigator, go to `CronJobs`.
+2. Select the target CronJob in the list.
+3. Press `e` to open the YAML editor view.
+4. Modify the content and save to submit.
+
+**Notes:**
+
+- Invalid or immutable field changes are rejected by the Kubernetes API.
+- If an update fails, adjust based on the error message and retry.
+- `Edit CronJob` opens in the `Action Workspace`. See [Action Workspace](../tutorial.md#action-workspace) for details.
+
+### Delete CronJob
+Deletes the currently selected CronJob resource.
+
+**Steps:**
+
+1. Select the target CronJob in the `CronJobs` list.
+2. Press `d` to trigger deletion.
+3. Confirm the action in the prompt.
+
+**Notes:**
+
+- Deletion removes the selected CronJob object from the cluster.
+- Check dependent workloads before deletion to avoid service impact.
+

kop_cli-0.2.0/docs/guide/DaemonSets.md

@@ -0,0 +1,65 @@
+# DaemonSets
+This document explains how to operate DaemonSets through kop.
+
+## Binding keys
+Available shortcuts for DaemonSet-related operations are shown in the Footer area at the bottom of the page. Available actions may vary slightly by context; always use the real-time prompts in the Footer as the source of truth.
+
+| Key | Action |
+| --- | --- |
+| `d` | Delete DaemonSet |
+| `e` | Edit DaemonSet |
+| `r` | Restart DaemonSet |
+| `n` | Next Page |
+| `p` | Previous Page |
+
+> Some `keys` are shown in the Footer only under specific conditions. For example, `n` and `p` are displayed only when the total number of resources exceeds the current screen height.
+
+## Actions
+The following sections describe what each action does and how to use it.
+
+### Restart DaemonSet
+Triggers a rolling restart for the selected DaemonSet.
+
+**Steps:**
+
+1. In the left resource navigator, go to `DaemonSets`.
+2. Select the target DaemonSet in the list.
+3. Press `r` to trigger restart.
+4. Confirm the action in the prompt.
+5. Monitor Pod replacement progress on each node.
+
+**Notes:**
+
+- Restart updates the Pod template restart annotation and performs a rolling replacement.
+- During rolling restart, old and new Pods may coexist briefly.
+
+### Edit DaemonSet
+Edits the DaemonSet YAML configuration and submits changes.
+
+**Steps:**
+
+1. In the left resource navigator, go to `DaemonSets`.
+2. Select the target DaemonSet in the list.
+3. Press `e` to open the YAML editor view.
+4. Modify the content and save to submit.
+
+**Notes:**
+
+- Invalid or immutable field changes are rejected by the Kubernetes API.
+- If an update fails, adjust based on the error message and retry.
+- `Edit DaemonSet` opens in the `Action Workspace`. See [Action Workspace](../tutorial.md#action-workspace) for details.
+
+### Delete DaemonSet
+Deletes the currently selected DaemonSet resource.
+
+**Steps:**
+
+1. Select the target DaemonSet in the `DaemonSets` list.
+2. Press `d` to trigger deletion.
+3. Confirm the action in the prompt.
+
+**Notes:**
+
+- Deletion removes the selected DaemonSet object from the cluster.
+- Check dependent workloads before deletion to avoid service impact.
+

kop_cli-0.2.0/docs/guide/Deployments.md

@@ -0,0 +1,79 @@
+# Deployments
+This document explains how to operate Deployments through kop.
+
+## Binding keys
+Available shortcuts for Deployment-related operations are shown in the Footer area at the bottom of the page. Available actions may vary slightly by context; always use the real-time prompts in the Footer as the source of truth.
+
+| Key | Action |
+| --- | --- |
+| `d` | Delete Deployment |
+| `e` | Edit Deployment |
+| `n` | Next Page |
+| `p` | Previous Page |
+| `r` | Restart Deployment |
+| `s` | Scale Deployment |
+
+> Some `keys` are shown in the Footer only under specific conditions. For example, `n` and `p` are displayed only when the total number of resources exceeds the current screen height.
+
+## Actions
+The following sections describe what each action does and how to use it.
+
+### Scale Deployment
+Scales the number of desired replicas for the selected Deployment.
+
+**Steps:**
+
+1. In the left resource navigator, go to `Deployments`.
+2. Select the target Deployment in the list.
+3. Press `s` to open the scale dialog.
+4. Enter the target replica count and confirm.
+5. Monitor Pod rollout status until the desired state is reached.
+
+**Notes:**
+
+- Scaling up creates more Pods; scaling down removes Pods.
+- Make sure cluster capacity and workload requirements match the target replica count.
+
+### Restart Deployment
+Triggers a rolling restart for the selected Deployment.
+
+**Steps:**
+
+1. Select the target Deployment in the `Deployments` list.
+2. Press `r` to trigger restart.
+3. Confirm the action in the prompt.
+4. Monitor rollout progress and Pod readiness.
+
+**Notes:**
+
+- Restart updates the Pod template restart annotation and performs a rolling replacement.
+- During rolling restart, old and new Pods may coexist briefly.
+
+### Edit Deployment
+Edits the Deployment YAML configuration and submits changes.
+
+**Steps:**
+
+1. Select the target Deployment.
+2. Press `e` to open the YAML editor view.
+3. Modify the content and save to submit.
+
+**Notes:**
+
+- Invalid or immutable field changes are rejected by the Kubernetes API.
+- If an update fails, adjust based on the error message and retry.
+- `Edit Deployment` opens in the `Action Workspace`. See [Action Workspace](../tutorial.md#action-workspace) for details.
+
+### Delete Deployment
+Deletes the currently selected Deployment resource.
+
+**Steps:**
+
+1. Select the target Deployment in the `Deployments` list.
+2. Press `d` to trigger deletion.
+3. Confirm the action in the prompt.
+
+**Notes:**
+
+- Deleting a Deployment stops controller management for its Pods.
+- ReplicaSet and Pod cleanup behavior depends on the deletion policy and current cluster state.