A k8s tui application management troubleshooting tool operation method

Abstract

The present invention relates to a method for operating a TUI application management troubleshooting tool for k8s, which at least includes step S1, starting TUI application management software and scanning the tools directory; step S2, traversing tool files to read configuration information and obtaining K8s related data; step S3, displaying a TUI interface after obtaining information about related data; step S4, a user inputting an operation instruction on the displayed TUI interface; step S5, executing the tool file. The TUI application management software of the present invention has a wide range of applications, and only needs to have shell operation capabilities, is applicable to cloud environments and systems or environments that do not provide a graphical user interface, and can enjoy a friendly user interface; constructs a graphical interface through text, which is convenient for operation and maintenance personnel to troubleshoot problems; the introduction of automated scripts makes it easy to locate common problems, and only requires selecting the corresponding tools; greatly improves work efficiency and also reduces maintenance costs.

Description

Technical Field

[0001] The present invention belongs to the field of computer operation and maintenance technology, and specifically relates to an operation method of a k8s tui application management troubleshooting tool. Background Art

[0002] Kubernetes, often referred to as k8s, is an open source container orchestration platform designed to automate the deployment, scaling, and management of containerized applications. It provides an easy way to deploy and run distributed systems, ensuring high availability and scalability of applications. With Kubernetes, developers and operations teams can manage containerized workloads more efficiently, thereby improving overall development and operations efficiency. The core functions of Kubernetes include automatic deployment, scaling, and load balancing of containerized applications. These functions are achieved by defining and managing the lifecycle of containers to ensure that applications run efficiently on each node in the cluster.

[0003] Kubernetes's architectural design is very flexible and supports a variety of different deployment environments, including physical machines, virtual machines, and cloud platforms. It manages cluster resources through a set of declarative APIs, allowing users to easily define and modify the state of applications. Kubernetes also provides a rich set of plug-ins and extension mechanisms, allowing users to customize and extend functions according to their needs.

[0004] In the existing related technical fields, Kubernetes adopts a troubleshooting method to ensure the stability and reliability of the system. This troubleshooting method is mainly achieved through the following aspects:

[0005] First, Kubernetes uses its powerful scheduling mechanism to distribute containers on different nodes to avoid single point failure. When a node fails, the system automatically migrates the container on the node to other healthy nodes to ensure the continuous operation of the service.

[0006] Secondly, Kubernetes implements troubleshooting through a health check mechanism. Each container will undergo a regular health check. If a container fails the health check, the system will automatically restart it or reschedule it to another node. This can effectively eliminate service interruptions caused by internal container failures.

[0007] In addition, Kubernetes also supports rolling updates and rollbacks, further enhancing the stability and reliability of the system. When updating applications, Kubernetes will gradually replace the old version of the container to ensure a smooth transition between the old and new versions. If a problem occurs during the update process, the system can quickly roll back to the old version, thus avoiding failures caused by the update.

[0008] Finally, Kubernetes also provides a wealth of monitoring and logging features to help administrators discover and troubleshoot problems in a timely manner. By monitoring the status of each container and node in real time, administrators can quickly locate problems and take appropriate measures to ensure the stable operation of the system.

[0009] Kubernetes ensures high availability and stability of the system through a variety of troubleshooting methods, such as node scheduling, health checks, rolling updates and rollbacks, as well as monitoring and logging functions. These mechanisms work together to make Kubernetes a powerful and reliable container orchestration platform.

[0010] In the current industry situation, troubleshooters face many challenges. First, they must have a deep understanding and familiarity with the entire system, which includes not only the system architecture and components, but also the interactions and dependencies between the various parts. Second, troubleshooters also need to be able to interpret log files, which means they must be able to extract key information from a large amount of log information in order to accurately identify the problem. This requires troubleshooters to have a high level of technical skills and rich experience, because they must be able to understand various information in the system log, including error codes, warning information, and system status.

[0011] Although the basic ideas for troubleshooting are usually fixed, in actual operation, manual inspection and processing are still required step by step. This means that troubleshooting requires patience and meticulousness, and every step cannot be sloppy to ensure that the problem can be solved thoroughly and avoid omissions or errors. Troubleshooters need to carefully analyze log files, check system configurations, verify network connections, and may even need to work with developers to ensure that the root cause of the problem is found and resolved.

[0012] The existing operation mode has at least the following shortcomings:

[0013] 1. A lot of human resources are needed in the troubleshooting process. Due to the complexity and diversity of the problems, it is sometimes easy to overlook some details. If the problem has been handled by others before, it may be necessary to sort it out again when troubleshooting again, which undoubtedly increases the workload and time cost.

[0014] 2. When dealing with problems, troubleshooters need to enter a large number of commands and analyze logs in detail. In many cases, these commands and log information are very complex and require cooperation and support from other personnel. This not only increases communication costs, but may also lead to inaccurate information transmission, thus affecting troubleshooting efficiency and accuracy.

[0015] 3. Commands are not easy to remember and cannot be used flexibly. Since the system commands are numerous and complex, troubleshooters may encounter difficulty in remembering them in actual operations, resulting in an inability to quickly find the right command to solve the problem. This situation will increase troubleshooting time, reduce work efficiency, and may even cause the problem to not be solved in time, affecting the stability and reliability of the entire system. Summary of the invention

[0016] In view of the defects of the current methods for troubleshooting k8s, the present invention proposes a method for operating a k8s tui application management troubleshooting tool, aiming to solve the problems of consuming a large amount of human resources, low troubleshooting efficiency and insufficient accuracy in the prior art. The present invention provides a special troubleshooting tool for operation and maintenance personnel to use, which has a friendly operation interface and a wide range of applications, making it convenient for relevant personnel to quickly troubleshoot.

[0017] To achieve the above purpose, the technical solution adopted by the present invention is: a method for operating a k8s tui application management troubleshooting tool, comprising at least the following steps:

[0018] Step S1, start the tui application management software and scan the tools directory;

[0019] Step S2, traverse the tool file to read the configuration information and obtain k8s related data;

[0020] Step S3, after obtaining the relevant data information, display the tui interface;

[0021] Step S4: the user inputs an operation instruction on the displayed tui interface;

[0022] Step S5: Execute the tool file.

[0023] Furthermore, the operation method of obtaining relevant data in step S2 at least includes the following:

[0024] S21. The tui application management scans all tool files under the tools directory of the same level. The tool files will provide functions for the tui application management software to call to obtain data related to the tool files;

[0025] S22, execute the baseInfo function of each tool file, obtain the tool name, tool description, and specific usage information and store them in the TOOLS variable;

[0026] S23, obtain the namespace and store it in the NAMESPACE variable;

[0027] S24. If there is a default namespace, set the value of the currently selected namespace variable CURRENT_NS to default. Otherwise, set the first value in the namespace as the value of CURRENT_NS.

[0028] S25. Get the pod information according to the namespace and store it in the PODS variable.

[0029] Further, in step S3, the content displayed in the tui application management includes at least four items;

[0030] The toolbar at the bottom is used to display the current namespace, tools, usage help, and return to the previous step;

[0031] The left area is the tool selection area, which displays the names of all scanned tools;

[0032] The middle service list area displays information about all pods in the namespace;

[0033] The right area is a workspace that displays help information, the tool execution process, the input of the execution process, and the execution status.

[0034] Furthermore, in step S4, the user inputs an operation instruction on the displayed tui interface, including at least any of the following operation modes:

[0035] The first operation mode: the user presses the "N" key, and the namespace selection pops up; in the selection interface, use the up and down arrow keys to select, use the "Enter" key to confirm, and use the "Esc" key to cancel; after confirmation, the CURRENT_NS value and the corresponding value of NS on the interface will be changed, and all pod information of the current namespace will be obtained and stored in the PODS variable, and the service list in the middle will be refreshed;

[0036] The second operation method: Press the "T" key to activate the tools area on the left. In this area, you can enter the number in front of the tool file to select the corresponding tool;

[0037] The third operation method: Pressing the "H" key will also activate the tools area on the left. After selecting a tool, the description information and usage instructions of the tool previously obtained will be displayed in the workspace area on the right;

[0038] The fourth operation mode: You can press the "B" key to return to the previous area, which has the same function as "Esc". The return function will return to the previous working area until the interface state when entering;

[0039] The fifth operation mode: Operation in the Tools area. If you press "H" to enter the help, the tool description and help information will be displayed directly in the right work area after pressing the number key in front of the tool.

[0040] If you select the service through the "T" tool, you will select the service; when there are more than 10 tools, paging information will be displayed, and you can switch the tools list by pressing the "P" key to go to the previous page and the "N" key to go to the next page.

[0041] Furthermore, the operation of the service list area is the same as that of the Tools area. After pressing the number key in front of the specified service, the getStatus function of the tool will be called to obtain the status and update the status information of the working area; then the invoke function will be executed to pass the current namespace and service information to the tui application management software.

[0042] Furthermore, the update implementation method of the tools in the tui application management software is as follows:

[0043] Create a new file with a different name in the program tools directory and implement the following method:

[0044] The baseInfo function returns a map type of data, in which title stores the name of the tool, desc stores a simple description of the software, and help stores the usage help of the software; the baseInfo function is used to obtain information about the tool file, including at least the name, a simple description, instructions for use, and whether one or more of the pods needs to be selected;

[0045] The invoke function will be called by the software after selecting the service information, and the current namespace and service information will be passed in;

[0046] The getStatus function will be called once before calling the invoke function, and will update the status information of the workspace. The getStatus function is a simple description or encoding of the execution result, which is convenient for positioning. It will also be called once after the invoke function is executed, and will also update the status information of the workspace.

[0047] The getNS function is used to obtain the current namespace. The value will be passed in as a parameter in the invoke function.

[0048] The getPodName function can get the currently selected pod. It is used to get the name of the currently executing pod. The value will be passed in as a parameter in the invoke function.

[0049] Furthermore, the method of replacing the certificate is implemented in the tui application management software:

[0050] Start the software, scan all tool files in the tools directory, traverse the tool files to read the configuration information, and obtain k8s related data;

[0051] The software obtains all namespaces;

[0052] The software obtains all pod information of the default namespace;

[0053] The software forms a UI interface through various texts and special symbols, and displays the TUI interface after obtaining relevant data information;

[0054] By default, when you press N in the tui interface, a tui for selecting a namespace will appear. After selecting, the Ns below the Enter key will switch. Press T to activate the Tools area, the title text will turn white, the background will turn gray, and the name of the tool will be displayed below the Tool after entering a number. Pressing the H key can also activate the Tools area, but the subsequent functions will display instructions for using this tool. Pressing the ESC key can return to the previous step, for example, from the main interface to the tool selection, pressing ESC will return to the main interface function.

[0055] Press the T key to activate the Tools area, then press the corresponding number key in front of the tool file, the tool in the bottom toolbar will be displayed as Change Certificate, and you will be switched to the tool for changing the certificate;

[0056] Since the certificate needs to be replaced by specifying a pod, the service list will be activated, and then press the number key to select the corresponding pod;

[0057] Execute the invoke function of tools / changeCret.sh; this function will receive relevant information, and then a box will appear to select the certificate location and certificate password;

[0058] After selecting the certificate location and entering the password, use the tab key to switch to the OK button. Press Enter to execute the replacement operation. At the same time, the status of the workspace is displayed as processing.

[0059] After execution is completed, the final result will be put into the workspace and the status will be updated to completed.

[0060] Furthermore, it also includes the expansion function of the tool. For the addition of new functions / new tools, users only need to copy the standardized files to the directory at the same level; using a modular expansion method, users do not need to perform complex configuration or programming to upgrade and maintain the tool, or add the latest functions / tools; and new functions can be quickly deployed and applied.

[0061] The technical solution adopted by the present invention has at least the following advantages: there is a lack of tools designed specifically for operation and maintenance personnel in the market; no tools for Kubernetes, i.e., K8s, have been found to use a text interface (i.e., a TUI interface); the TUI application management software of the present invention has a wide range of applications and only requires shell operation capabilities (applicable to cloud environments and systems or environments that do not provide a graphical user interface) to enjoy a friendly user interface; it has high scalability and only requires adding a specific file to achieve functional expansion without interfering with existing functions.

[0062] The technical solution provided in the present invention also has the following advantages:

[0063] 1. By converting text information into a graphical interface, the efficiency and accuracy of operation and maintenance personnel in troubleshooting can be greatly improved. This graphical interface not only intuitively displays detailed information about the problem, but also helps operation and maintenance personnel quickly locate the root cause of the problem, thereby effectively shortening the time to solve the problem.

[0064] 2. In the existing technical field, locating the fault point is usually a complex and tedious process, which requires not only maintenance personnel to have deep professional skills but also rich practical experience. However, the present invention greatly simplifies this process by introducing automated scripts. Now, operation and maintenance personnel only need to select the corresponding tools to easily locate common problems without having to perform tedious manual operations, which greatly reduces the requirements for professional skills and experience.

[0065] 3. Once these tools are written, they can be reused in different environments without rewriting. This means that the operation and maintenance team can save a lot of time and energy because they do not need to redevelop and debug tools for each new environment. This reusable feature greatly improves work efficiency and reduces maintenance costs.

[0066] 4. The tool is designed to be easy to use for users without a deep technical background. Through simple learning and practice, even beginners can quickly master the use of the tool and effectively troubleshoot and solve problems. This ease of use allows more people to participate in the problem-solving process, thereby improving the collaboration efficiency of the entire team.

[0067] 5. The process of adding new functions is also very simple. Users only need to copy standardized files to the specified directory. This modular expansion method not only makes it easier to upgrade and maintain the tool, but also ensures the rapid deployment and application of new functions. Users can enjoy the latest functions and improvements without complex configuration or programming, which greatly improves the flexibility and adaptability of the tool. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0069] Figure 1 It is a schematic diagram of loading flow in the tui application management operation method of the present invention;

[0070] Figure 2 It is a schematic diagram of the interface of the tui application management software of the present invention;

[0071] Figure 3 It is a schematic diagram of the entity structure in the tui application management software of the present invention. DETAILED DESCRIPTION

[0072] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.

[0073] See also Figure 1 and Figure 2 As shown, this embodiment provides a method for operating a k8s tui application management troubleshooting tool, which includes at least the following steps:

[0074] Step S1, start the tui application management software and scan the tools directory;

[0075] Step S2, traverse the tool file to read the configuration information and obtain k8s related data;

[0076] Step S3, after obtaining the relevant data information, display the tui interface;

[0077] Step S4: the user inputs an operation instruction on the displayed tui interface;

[0078] Step S5: Execute the tool file.

[0079] As a preferred implementation, in this embodiment, the operation method for obtaining relevant data in step S2 at least includes the following: when the tui application management software is started, some kubernetes or K8S related data will be obtained first.

[0080] S21. The tui application management scans all tool files under the tools directory at the same level. The tool files provide functions for the tui application management software to call to obtain data related to the tool files. In this embodiment, the tool files are also commonly known as script files.

[0081] S22, execute the baseInfo function of each tool file, obtain the tool name, tool description, and specific usage information and store them in the TOOLS variable;

[0082] S23, obtain the namespace and store it in the NAMESPACE variable;

[0083] S24. If there is a default namespace, set the CURRENT_NS (currently selected namespace) variable value to default; otherwise, set the first value in the namespace as the value of CURRENT_NS.

[0084] S25. Get the pod information according to the namespace and store it in the PODS variable.

[0085] As a preferred implementation, in this embodiment, please refer to Figure 1 As shown, in step S3, the content displayed in the tui application management includes at least four items;

[0086] The toolbar at the bottom is used to display the current namespace, tools, usage help, and return to the previous step;

[0087] The left area is the tool selection area, which displays the names of all scanned tools;

[0088] The middle service list area displays information about all pods in the namespace;

[0089] The right area is a workspace that displays help information, the tool execution process, the input of the execution process, and the execution status.

[0090] As a preferred implementation, in this embodiment, in step S4, the user inputs an operation instruction on the displayed tui interface, including at least any of the following operation modes:

[0091] The first operation mode: the user presses the "N" key, and the namespace selection pops up; in the selection interface, use the up and down arrow keys to select, use the "Enter" key to confirm, and use the "Esc" key to cancel; after confirmation, the CURRENT_NS value and the corresponding value of NS on the interface will be changed, and all pod information of the current namespace will be obtained and stored in the PODS variable, and the service list in the middle will be refreshed;

[0092] The second operation method: Press the "T" key to activate the tools area on the left. In this area, you can enter the number in front of the tool file to select the corresponding tool;

[0093] The third operation method: Pressing the "H" key will also activate the tools area on the left. After selecting a tool, the description information and usage instructions of the tool previously obtained will be displayed in the workspace area on the right;

[0094] The fourth operation mode: You can press the "B" key to return to the previous area, which has the same function as "Esc". The return function will return to the previous working area until the interface state when entering;

[0095] The fifth operation mode: Operation in the Tools area. If you press "H" to enter the help, the tool description and help information will be displayed directly in the right work area after pressing the number key in front of the tool.

[0096] If you select the service through the "T" tool, you will select the service; when there are more than 10 tools, paging information will be displayed, and you can switch the tools list by pressing the "P" key to go to the previous page and the "N" key to go to the next page.

[0097] In this embodiment, it is necessary to add that the operation of the service list area is the same as that of the Tools area. After pressing the number key in front of the specified service, the getStatus function of the tool will be called to obtain the status and update the status information of the working area; then the invoke function will be executed to pass the current namespace and service information to the tui application management software. The title of the current area will become the original inverted color.

[0098] As a preferred implementation, in this embodiment, please refer to Figure 3As shown, the update implementation method of the tools in the tui application management software is:

[0099] Create a new file with a different name in the program tools directory and implement the following method:

[0100] The baseInfo function returns a map type of data, in which title stores the name of the tool, desc stores a simple description of the software, and help stores the usage help of the software; the baseInfo function is used to obtain information about the tool file, including at least the name, a simple description, instructions for use, and whether one or more of the pods needs to be selected;

[0101] The invoke function will be called by the software after selecting the service information, and the current namespace and service information will be passed in;

[0102] The getStatus function will be called once before calling the invoke function, and will update the status information of the workspace. The getStatus function is a simple description or encoding of the execution result, which is convenient for positioning. It will also be called once after the invoke function is executed, and will also update the status information of the workspace.

[0103] The getNS function is used to obtain the current namespace. The value will be passed in as a parameter in the invoke function.

[0104] The getPodName function can get the currently selected pod. It is used to get the name of the currently executing pod. The value will be passed in as a parameter in the invoke function.

[0105] like Figure 3 As shown in the figure, it is equivalent to a standard specification, in which the method (function) will be called by the tool, and the method will return specific parameter information, execution command and result. Taking the inability to obtain the stream as an example, it is necessary to implement the baseInfo function, which will return the title value "Inability to obtain the stream", and the help value describes the operation instructions that the stream extraction tool will perform. The invoke function is responsible for executing commands such as log retrieval and network retrieval, and returns the corresponding results, including the reason why the stream cannot be obtained. As for the file copy command, the title value returned by the baseInfo function is file copy, and the help value provides instructions for performing the file copy operation, including the required parameters, and the invoke function is responsible for copying the file to the local directory after the user selects the file.

[0106] As another embodiment, in this embodiment, please refer to Figure 1 and Figure 2 As shown, this embodiment provides a method for implementing certificate replacement in tui application management software:

[0107] Start the software, scan all tool files in the tools directory, traverse the tool files to read the configuration information, and obtain k8s related data;

[0108] The software obtains all namespaces;

[0109] The software obtains all pod information of the default namespace; in the present invention, pod means an application.

[0110] The software forms a UI interface through various texts and special symbols, and displays the TUI interface after obtaining relevant data information;

[0111] By default, when you press N in the tui interface, a tui for selecting a namespace will appear. After selecting, the Ns below the Enter key will switch. Press T to activate the Tools area, the title text will turn white, the background will turn gray, and the name of the tool will be displayed below the Tool after entering a number. Pressing the H key can also activate the Tools area, but the subsequent functions will display instructions for using this tool. Pressing the ESC key can return to the previous step, for example, from the main interface to the tool selection, pressing ESC will return to the main interface function.

[0112] Press the T key to activate the Tools area, then press the number key corresponding to the tool file (for example, Figure 2 , select Tools area and correct the number in front of the certificate. 2) The tool bar at the bottom will show "Change Certificate", and you will switch to the tool for changing the certificate.

[0113] Since the certificate needs to be replaced by specifying a pod, the service list will be activated, and then press the number key to select the corresponding pod;

[0114] Execute the invoke function of tools / changeCret.sh; this function will receive relevant information, and then a box will appear to select the certificate location and certificate password;

[0115] After selecting the certificate location and entering the password, use the tab key to switch to the OK button. Press Enter to execute the replacement operation. At the same time, the status of the workspace is displayed as processing.

[0116] After execution is completed, the final result will be put into the workspace and the status will be updated to completed.

[0117] Press the ESC key to return to the service list, press ECS again to go to the Tools area, and press ESC again to go to the start interface.

[0118] As an implementation method, this embodiment also includes the expansion function of the tool. For the addition of new functions / new tools, the user only needs to copy the standardized files to the directory of the same level; using a modular expansion method, the user does not need to perform complex configuration or programming to upgrade and maintain the tool, or add the latest functions / tools; and realizes the rapid deployment and application of new functions.

[0119] The process of adding new features is also very simple. Users only need to copy standardized files to the specified directory. This modular expansion method not only makes it easier to upgrade and maintain the tool, but also ensures the rapid deployment and application of new features. Users can enjoy the latest features and improvements without complex configuration or programming, which greatly improves the flexibility and adaptability of the tool.

[0120] like Figure 2 As shown, it should be noted that the present embodiment is only an illustrative specific operation method, and other commands can be executed as needed. For example, operations such as log viewing, cleaning abnormal POD services, unable to obtain streams, and file copying can be performed. No detailed description is given here. The present invention aims to solve the problems of the prior art that troubleshooting requires a lot of human resources, low troubleshooting efficiency, and insufficient accuracy. The present invention provides a special troubleshooting tool for use by operation and maintenance personnel. The tool has a friendly operation interface and a wide range of applications, which is convenient for relevant personnel to quickly troubleshoot.

[0121] Although the embodiments of the present invention have been shown and described above, it will be appreciated that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, substitute and vary the above embodiments within the scope of the present invention.

Claims

1. A method for operating a k8s tui application management troubleshooting tool, characterized in that: At least the following steps are included: By using this method, operation and maintenance personnel only need to select corresponding tools to locate common problems without having to perform tedious manual operations; Step S1, start the tui application management software and scan the tools directory; Step S2, traverse the tool file to read the configuration information and obtain k8s related data; Step S3, after obtaining the relevant data information, display the tui interface; Step S4: the user inputs an operation instruction on the displayed tui interface; Step S5, executing tool file; The operation method of obtaining relevant data in step S2 at least includes the following: S21. The tui application management scans all tool files under the tools directory of the same level. The tool files will provide functions for the tui application management software to call to obtain data related to the tool files; S22, execute the baseInfo function of each tool file, obtain the tool name, tool description, and specific usage information and store them in the TOOLS variable; S23, obtain the namespace and store it in the NAMESPACE variable; S24. If there is a default namespace, set the value of the currently selected namespace variable CURRENT_NS to default. Otherwise, set the first value in the namespace as the value of CURRENT_NS. S25. Get the pod information according to the namespace and store it in the PODS variable; In step S3, the content displayed in the tui application management includes at least four items; The toolbar at the bottom is used to display the current namespace, tools, usage help, and return to the previous step; The left area is the tool selection area, which displays the names of all scanned tools; The middle service list area displays information about all pods in the namespace; The right area is a workspace that displays help information, the tool execution process, the input of the execution process, and the status of the execution; In step S4, the user inputs an operation instruction on the displayed tui interface, which includes at least any of the following operation modes: The first operation mode: the user presses the "N" key, and the namespace selection pops up; in the selection interface, use the up and down arrows to select, use the "Enter" key to confirm, and the "Esc" key to cancel; after confirmation, the CURRENT_NS value and the corresponding value of NS on the interface will be changed, and all pod information of the current namespace will be obtained and stored in the PODS variable, and the service list in the middle will be refreshed; The second operation method: Press the "T" key to activate the tools area on the left. In this area, you can enter the number in front of the tool file to select the corresponding tool; The third operation method: Pressing the "H" key will also activate the tools area on the left. After selecting a tool, the description information and usage instructions of the tool previously obtained will be displayed in the workspace area on the right; The fourth operation method: You can press the "B" key to return to the previous area, which has the same function as "Esc". The return function will return to the previous working area until the interface state when entering; The fifth operation mode: Operation in the Tools area. If you press "H" to enter the help, the tool description and help information will be displayed directly in the right work area after pressing the number key in front of the tool. If you select the service through the "T" tool, you will select the service. When there are more than 10 tools, the paging information will be displayed. You can switch the tools list by pressing the "P" key to go to the previous page and the "N" key to go to the next page. The operation of the service list area is the same as that of the Tools area. After pressing the number key in front of the specified service, the getStatus function of the tool will be called to obtain the status and update the status information of the work area; then the invoke function will be executed to pass the current namespace and service information to the tui application management software; How to update tools in tui application management software: Create a new file with a different name in the program tools directory and implement the following method: The baseInfo function returns a map type of data, in which title stores the name of the tool, desc stores a simple description of the software, and help stores the usage help of the software; the baseInfo function is used to obtain information about the tool file, including at least the name, a simple description, instructions for use, and whether one or more of the pods needs to be selected; The invoke function will be called by the software after selecting the service information, and the current namespace and service information will be passed in; The getStatus function will be called once before calling the invoke function, and will update the status information of the workspace. The getStatus function is a simple description or encoding of the execution result, which is convenient for positioning. It will also be called once after the invoke function is executed, and will also update the status information of the workspace. The getNS function is used to obtain the current namespace. The value will be passed in as a parameter in the invoke function. The getPodName function can get the currently selected pod. It is used to get the name of the currently executing pod. The value will be passed in as a parameter in the invoke function. How to change the certificate in the tui application management software: Start the software, scan all tool files in the tools directory, traverse the tool files to read the configuration information, and obtain k8s related data; The software obtains all namespaces; The software obtains all pod information of the default namespace; The software forms a UI interface through various texts and special symbols, and displays the TUI interface after obtaining relevant data information; By default, when you press N in the tui interface, a tui for selecting a namespace will appear. After selecting, the Ns below the Enter key will switch. Press T to activate the Tools area, the title text will turn white, the background will turn gray, and the name of the tool will be displayed below the Tool after entering a number. Pressing the H key can also activate the Tools area, but the subsequent functions will display instructions for using this tool. Pressing the ESC key can return to the previous step, for example, from the main interface to the tool selection, pressing ESC will return to the main interface function. Press the T key to activate the Tools area, then press the corresponding number key in front of the tool file, the tool in the bottom toolbar will be displayed as Change Certificate, and you will be switched to the tool for changing the certificate; Since the certificate needs to be replaced by specifying a pod, the service list will be activated, and then press the number key to select the corresponding pod; Execute the invoke function of tools / changeCret.sh; this function will receive relevant information, and then a box will appear to select the certificate location and certificate password; After selecting the certificate location and entering the password, use the tab key to switch to the OK button. Press Enter to execute the replacement operation. At the same time, the status of the workspace is displayed as processing. After execution is completed, the final result will be put into the workspace and the status will be updated to completed.

2. The method according to claim 1, characterized in that: It also includes the tool's expansion functions. To add new functions / new tools, users only need to copy standardized files to the same-level directory. With a modular expansion approach, users do not need to perform complex configuration or programming to upgrade and maintain tools, or add the latest functions / tools. Rapid deployment and application of new functions is achieved.

Images