zh, en: remove tkctl (#2470) (#2471)

pingcap · Nov 28, 2023 · be3ce15 · be3ce15
1 parent 31312fa
commit be3ce15
Show file tree

Hide file tree

Showing 9 changed files with 10 additions and 833 deletions.
diff --git a/en/TOC.md b/en/TOC.md
@@ -117,7 +117,6 @@
   - [Cheat Sheet](cheat-sheet.md)
   - [Required RBAC Rules](tidb-operator-rbac.md)
   - Tools
-    - [tkctl](use-tkctl.md)
     - [TiDB Toolkit](tidb-toolkit.md)
   - Configure
     - [Configure tidb-drainer Chart](configure-tidb-binlog-drainer.md)

diff --git a/en/maintain-a-kubernetes-node.md b/en/maintain-a-kubernetes-node.md
@@ -13,7 +13,6 @@ This document introduces how to perform a temporary or long-term maintenance tas
 ## Prerequisites
 
 - [`kubectl`](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
-- [`tkctl`](use-tkctl.md)
 - [`jq`](https://stedolan.github.io/jq/download/)
 
 > **Note:**

diff --git a/en/network-issues.md b/en/network-issues.md
@@ -32,10 +32,10 @@ When you find some network connection issues among Pods from the log or monitori
     {{< copyable "shell-regular" >}}
 
     ```shell
-    tkctl debug -n ${namespace} ${pod_name}
+    kubectl -n ${namespace} exec -it ${pod_name} -- sh
     ```
 
-    After the remote shell is started, use the `dig` command to diagnose the DNS resolution. If the DNS resolution is abnormal, refer to [Debugging DNS Resolution](https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/) for troubleshooting.
+    Use the `dig` command to diagnose the DNS resolution. If the DNS resolution is abnormal, refer to [Debugging DNS Resolution](https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/) for troubleshooting.
 
     {{< copyable "shell-regular" >}}
 
@@ -53,15 +53,9 @@ When you find some network connection issues among Pods from the log or monitori
 
     - If the `ping` check fails, refer to [Debugging Kubernetes Networking](https://www.praqma.com/stories/debugging-kubernetes-networking/) for troubleshooting.
 
-    - If the `ping` check succeeds, continue to check whether the target port is open by using `telnet`:
+    - If the `ping` check succeeds, continue to check whether the target port is open by using `wget` or `curl`.
 
-        {{< copyable "shell-regular" >}}
-
-        ```shell
-        telnet ${TARGET_IP} ${TARGET_PORT}
-        ```
-
-        If the `telnet` check fails, check whether the port corresponding to the Pod is correctly exposed and whether the port of the application is correctly configured:
+        If the `wget` or `curl` check fails, check whether the port corresponding to the Pod is correctly exposed and whether the port of the application is correctly configured:
 
         {{< copyable "shell-regular" >}}
 

diff --git a/en/tidb-operator-overview.md b/en/tidb-operator-overview.md
@@ -61,9 +61,6 @@ When a problem occurs and the cluster needs diagnosis, you can:
 + See [TiDB FAQs on Kubernetes](faq.md) for any available solution;
 + See [Troubleshoot TiDB on Kubernetes](tips.md) to shoot troubles.
 
-TiDB on Kubernetes provides a dedicated command-line tool `tkctl` for cluster management and auxiliary diagnostics. Meanwhile, some of TiDB's tools are used differently on Kubernetes. You can:
-
-+ Use `tkctl` according to [`tkctl` Guide](use-tkctl.md );
-+ See [Tools on Kubernetes](tidb-toolkit.md) to understand how TiDB tools are used on Kubernetes.
+Some of TiDB's tools are used differently on Kubernetes. You can see [Tools on Kubernetes](tidb-toolkit.md) to understand how TiDB tools are used on Kubernetes.
 
 Finally, when a new version of TiDB Operator is released, you can refer to [Upgrade TiDB Operator](upgrade-tidb-operator.md) to upgrade to the latest version.