Kubernetes cluster resource visualization system

Abstract

The invention discloses a Kubernetes cluster resource visualization system, and relates to the technical field of Kubernetes. The system comprises a Kubernetes cluster resource grouping module which is used for grouping Kubernetes cluster resources and outputting a Kubernetes cluster resource grouping result; the Kubernetes cluster resource monitoring module is used for monitoring the Kubernetes cluster resource and outputting a Kubernetes cluster resource monitoring result, and the Kubernetes cluster resource monitoring module is used for monitoring the Kubernetes cluster resource; and the Kubernetes cluster resource visualization module is used for carrying out visualization display on the Kubernetes cluster resources according to the grouping result of the Kubernetes cluster resources and the monitoring result of the Kubernetes cluster resources. According to the Kubernetes cluster resource visualization method and device, the practicability of Kubernetes cluster resource visualization can be improved.

Description

Technical Field

[0001] The present application relates to the field of Kubernetes technology, and in particular to a Kubernetes cluster resource visualization system. Background Art

[0002] As the de facto standard in the field of container orchestration, Kubernetes has been widely used in the deployment and management of cloud-native applications. It allows users to automate the deployment, expansion and management of containerized applications, greatly improving the speed and flexibility of application delivery. However, as the scale of Kubernetes clusters grows, the complexity of resource management and monitoring also increases.

[0003] Currently, most Kubernetes cluster management tools provide basic resource viewing and monitoring functions. However, when faced with hundreds or thousands of Pods, services, and other resources, these management tools lack effective mechanisms to help users simplify the organization and classification of these resources, resulting in the provided view information being impractical for some user groups. Summary of the invention

[0004] The main purpose of this application is to provide a Kubernetes cluster resource visualization system, aiming to solve the technical problem of insufficient practicality of visualization of Kubernetes cluster resources in related technologies.

[0005] To achieve the above objectives, the present application provides a Kubernetes cluster resource visualization system, the system comprising: A Kubernetes cluster resource grouping module, used to group the Kubernetes cluster resources and output the Kubernetes cluster resource grouping results; A Kubernetes cluster resource monitoring module, used to monitor the Kubernetes cluster resources and output Kubernetes cluster resource monitoring results; The Kubernetes cluster resource visualization module is used to visualize the Kubernetes cluster resources according to the Kubernetes cluster resource grouping results and the Kubernetes cluster resource monitoring results.

[0006] In one embodiment, the Kubernetes cluster resource grouping module includes: A service grouping unit, configured to group the Pods in the Kubernetes cluster resources to obtain a service grouping result, wherein the service grouping result includes at least one service group, and the service group includes at least one Pod; an application grouping unit, configured to group the service groups in the service grouping result to obtain an application grouping result, wherein the application grouping result includes at least one application group, and the application group includes at least one service group; The Kubernetes cluster resource grouping result includes the service grouping result and the application grouping result.

[0007] In one embodiment, the Kubernetes cluster resource grouping module further includes: A project grouping unit, configured to group the application groups in the application grouping result to obtain a project grouping result, wherein the project grouping result includes at least one project grouping, and the project grouping includes at least one application grouping; A department grouping unit, used for grouping the project groups in the project grouping result to obtain a department grouping result, wherein the department grouping result includes at least one department grouping, and the department grouping includes at least one project grouping; The Kubernetes cluster resource grouping results include the service grouping results, the application grouping results, the project grouping results and the department grouping results.

[0008] In one embodiment, the Kubernetes cluster resource monitoring module includes: A Pod monitoring unit, configured to monitor the Pods in the Kubernetes cluster resources and output Pod monitoring results, wherein the Pod monitoring results include monitoring results of at least one Pod; The Kubernetes cluster resource monitoring results include the Pod monitoring results.

[0009] In one embodiment, the Pod monitoring unit is further used to: When receiving a monitoring instruction for a target Pod, monitor the target Pod and output a target Pod monitoring result, wherein the target Pod monitoring result is a monitoring result of the target Pod; In case of receiving a monitoring instruction for a target service group, monitoring the target service group and outputting a monitoring result of the target service group, wherein the monitoring result of the target service group includes monitoring results of all Pods in the target service group; In case of receiving a monitoring instruction for a target application group, monitoring the target application group and outputting a monitoring result of the target application group, wherein the monitoring result of the target application group includes monitoring results of all service groups in the target application group; The Pod monitoring result includes at least one of the target Pod monitoring result, the target service group monitoring result and the target application group monitoring result.

[0010] In one embodiment, the Kubernetes cluster resource visualization module is further used to: When receiving a visual display instruction for a target service group, visually display the target service group according to the monitoring result of the target service group; When a visual display instruction for a target application group is received, the target application group is visually displayed according to the monitoring result of the target application group.

[0011] In one embodiment, the visualization is performed by means of a topology relationship diagram, wherein the topology relationship diagram is a static topology relationship diagram or a dynamic topology relationship diagram.

[0012] In one embodiment, the Kubernetes cluster resource visualization module is further used to: When receiving a folding instruction for a target service group, folding the target service group in the topology relationship graph; In case of receiving a folding instruction for a target application group, the target application group is folded in the topology relationship graph.

[0013] In one embodiment, the monitoring result includes a result of monitoring the operating status, and the visual display includes visualization of the operating status.

[0014] In one embodiment, the icon of each topological node in the topological relationship diagram allows for custom settings.

[0015] The present application provides a Kubernetes cluster resource visualization system, which relates to the field of Kubernetes technology. The system consists of a Kubernetes cluster resource grouping module, a Kubernetes cluster resource monitoring module and a Kubernetes cluster resource visualization module. Among them, the Kubernetes cluster resource grouping module allows users to customize the grouping of complex and scattered resources in large-scale Kubernetes clusters according to actual needs. Through flexible grouping rule settings, such as based on namespaces, labels, resource types, etc., users can classify similar or related resources together, thereby simplifying the organization and management of resources, reducing operation complexity, and improving operation and maintenance efficiency. On the basis of grouping, the Kubernetes cluster resource monitoring module allows users to implement customized monitoring strategies for Kubernetes cluster resources in each group. Users can choose to focus on specific types of indicators (such as CPU usage, memory consumption, network traffic, etc.) according to different business scenarios or role requirements, and set threshold alarm mechanisms. This refined monitoring method not only enhances the effectiveness of monitoring, but also enables key performance issues to be discovered and handled in a timely manner, ensuring the stable operation of the system. The Kubernetes cluster resource visualization module combines the grouping results and monitoring results to provide an intuitive and interactive visualization display method. It uses a graphical interface to present the overall health status of the cluster, the relationship between resource groups, and their dynamic change trends, helping users quickly understand complex cluster environments. In addition, the visual dashboard supports real-time updates, and users can deeply explore the status of specific resources by clicking, filtering, etc., to help make more informed decisions.

[0016] Through the mutual cooperation of the above modules in the Kubernetes cluster resource visualization system, the present application effectively solves the technical problem of insufficient practicality of visualization of Kubernetes cluster resources in related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0018] In order to more clearly illustrate the embodiments of the present application 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 application. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying any creative work.

[0019] Figure 1This is a schematic diagram of the module structure of the Kubernetes cluster resource visualization system in the embodiment of the present application; Figure 2 This is a schematic diagram of the first structure of the Kubernetes cluster resource grouping module in an embodiment of the present application; Figure 3 This is a second structural diagram of the Kubernetes cluster resource grouping module in an embodiment of the present application; Figure 4 This is a schematic diagram of the first structure of the Kubernetes cluster resource monitoring module in an embodiment of the present application; Figure 5 This is a second structural diagram of the Kubernetes cluster resource monitoring module in an embodiment of the present application.

[0020] Figure structure description: 100. Kubernetes cluster resource visualization system; 1. Kubernetes cluster resource grouping module, 11. Service grouping unit, 12. Application grouping unit, 13. Project grouping unit, 14. Department grouping unit; 2. Kubernetes cluster resource monitoring module, 21. Pod monitoring unit, 22. Service monitoring unit, 23. Controller monitoring unit; 3. Kubernetes cluster resource visualization module.

[0021] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0022] 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 implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0023] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0024] Currently, most Kubernetes cluster management tools provide basic resource viewing and monitoring functions. However, when faced with hundreds or thousands of Pods, services, and other resources, these management tools lack effective mechanisms to help users simplify the organization and classification of these resources, resulting in the provided view information being impractical for some user groups.

[0025] The main solution of this application is a Kubernetes cluster resource visualization system, which includes: a Kubernetes cluster resource grouping module, which is used to group the Kubernetes cluster resources and output the Kubernetes cluster resource grouping results; a Kubernetes cluster resource monitoring module, which is used to monitor the Kubernetes cluster resources and output the Kubernetes cluster resource monitoring results; a Kubernetes cluster resource visualization module, which is used to visualize the Kubernetes cluster resources according to the Kubernetes cluster resource grouping results and the Kubernetes cluster resource monitoring results.

[0026] In this application, the Kubernetes cluster resource visualization system consists of a Kubernetes cluster resource grouping module, a Kubernetes cluster resource monitoring module, and a Kubernetes cluster resource visualization module. Among them, the Kubernetes cluster resource grouping module allows users to customize the grouping of complex and scattered resources in large-scale Kubernetes clusters according to actual needs. Through flexible grouping rule settings, such as based on namespaces, labels, resource types, etc., users can classify similar or related resources together, thereby simplifying the organization and management of resources, reducing operational complexity, and improving operation and maintenance efficiency. On the basis of grouping, the Kubernetes cluster resource monitoring module allows users to implement customized monitoring strategies for Kubernetes cluster resources in each group. Users can choose to focus on specific types of indicators (such as CPU usage, memory consumption, network traffic, etc.) according to different business scenarios or role requirements, and set threshold alarm mechanisms. This refined monitoring method not only enhances the effectiveness of monitoring, but also enables key performance issues to be discovered and handled in a timely manner, ensuring the stable operation of the system. The Kubernetes cluster resource visualization module combines grouping results and monitoring results to provide an intuitive and interactive visualization display method. It presents the overall health of the cluster, the relationship between resource groups, and their dynamic change trends in a graphical interface to help users quickly understand complex cluster environments. In addition, the visual dashboard supports real-time updates, and users can deeply explore the status of specific resources by clicking, filtering, etc., to help make more informed decisions.

[0027] Through the mutual cooperation of the above modules in the Kubernetes cluster resource visualization system, the present application effectively solves the technical problem of insufficient practicality of visualization of Kubernetes cluster resources in related technologies.

[0028] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0029] Please refer to Figure 1 , Figure 1 This is a schematic diagram of the module structure of the Kubernetes cluster resource visualization system in an embodiment of the present application.

[0030] In this embodiment, the Kubernetes cluster resource visualization system 100 includes: Kubernetes cluster resource grouping module 1, used to group Kubernetes cluster resources and output the Kubernetes cluster resource grouping results; Kubernetes cluster resource monitoring module 2 is used to monitor Kubernetes cluster resources and output Kubernetes cluster resource monitoring results; The Kubernetes cluster resource visualization module 3 is used to visualize the Kubernetes cluster resources according to the Kubernetes cluster resource grouping results and the Kubernetes cluster resource monitoring results.

[0031] Those skilled in the art will know that Kubernetes (often referred to as K8s) is an open source platform for automating the deployment, expansion and management of containerized applications. Kubernetes cluster resources refer to physical or logical entities that can be managed and scheduled in a Kubernetes cluster.

[0032] In this embodiment, Kubernetes cluster resources mainly include Pod (container group), Service (service), Controller (controller), Namespace (namespace), etc.

[0033] In this embodiment, the Kubernetes cluster resource grouping module 1 allows users to customize the grouping of complex and scattered resources in a large-scale Kubernetes cluster according to actual needs. Through flexible grouping rule settings, such as based on namespaces, labels, resource types, etc., users can classify similar or related resources together, thereby simplifying the organization and management of resources, reducing operational complexity, and improving operation and maintenance efficiency.

[0034] For example, Figure 2 As shown, in a feasible implementation, the Kubernetes cluster resource grouping module 1 includes: A service grouping unit 11 is used to group the Pods in the Kubernetes cluster resources to obtain a service grouping result, wherein the service grouping result includes at least one service group, and the service group includes at least one Pod; An application grouping unit 12, configured to group the service groups in the service grouping result to obtain an application grouping result, wherein the application grouping result includes at least one application group, and the application group includes at least one service group; The Kubernetes cluster resource grouping results include service grouping results and application grouping results.

[0035] In this embodiment, a cloud native application deployed through Kubernetes is usually composed of at least one microservice, each microservice corresponds to at least one microservice instance, and a microservice instance usually corresponds to a Pod.

[0036] Based on this, this embodiment sets the Kubernetes cluster resource grouping module 1 to include a service grouping unit 11 and an application grouping unit 12. Among them, the service grouping unit 11 allows the user to group the Pods in the Kubernetes cluster resources. For example, the user can group the Pods with the same business logic and the same functions into the same service group. At this time, a specific service group corresponds to a specific microservice, and each Pod in the service group corresponds to a specific instance of the microservice. The application grouping unit 12 allows the user to group the service groups in the service grouping results. For example, the user can group the service groups that belong to the same cloud native application and can fully implement the various service functions of the cloud native application after combination into the same application group. At this time, a specific application group corresponds to a specific cloud native application, and each service group in the application group corresponds to a microservice required to constitute the cloud native application.

[0037] Through the service grouping unit 11 and the application grouping unit 12, this embodiment realizes the multi-level and multi-dimensional grouping of large-scale Kubernetes cluster resources, and the gradual grouping process from Pod to service and then to application makes the originally complex and scattered resources orderly and easy to manage, reduces the operation complexity, and improves the operation and maintenance efficiency. The grouped Kubernetes cluster resources can be presented to the user in a more intuitive way, making it easier for the user to understand and operate the cluster resources, thereby improving the overall user experience.

[0038] It is understandable that, in addition to creating groups, each grouping unit can also implement operations such as group management, deletion and update.

[0039] Furthermore, if Figure 3As shown, in another feasible implementation, the Kubernetes cluster resource grouping module 1 further includes: The project grouping unit 13 is used to group the application groups in the application grouping result to obtain a project grouping result, wherein the project grouping result includes at least one project grouping, and the project grouping includes at least one application grouping; The department grouping unit 14 is used to group the project groups in the project grouping result to obtain a department grouping result, wherein the department grouping result includes at least one department grouping, and the department grouping includes at least one project grouping; The Kubernetes cluster resource grouping results include service grouping results, application grouping results, project grouping results, and department grouping results.

[0040] In this implementation, according to the organizational structure of an enterprise, an enterprise usually has multiple departments, a department may be responsible for one or more projects, and each project involves one or more applications.

[0041] Based on this, this implementation scheme sets the Kubernetes cluster resource grouping module 1 to also include a project grouping unit 13 and a department grouping unit 14, thereby allowing users to group applications belonging to the same project into the same project grouping, and group project groups belonging to the same department into the same department grouping, thereby achieving a direct mapping between the grouping logic of Kubernetes cluster resources and the organizational structure of the enterprise, making cluster management more in line with business needs, facilitating different departments or teams to collaborate efficiently on the same platform, ensuring that everyone focuses on the part they are responsible for, while maintaining information sharing and coordination, so that senior managers of the enterprise can get an overview of the distribution of Kubernetes cluster resources from the department and project levels when using this system to visualize Kubernetes cluster resources, helping them make more informed strategic decisions.

[0042] It should be noted that in this implementation, members at different levels in the enterprise have different permissions. For example, only managers at the department level and above have the relevant permissions to perform Kubernetes cluster resource grouping, monitoring, and visualization operations at the department level.

[0043] This implementation method achieves deep integration of the Kubernetes cluster resource grouping module into the enterprise organizational structure by introducing the project grouping unit 13 and the department grouping unit 14, enhances the granularity and flexibility of resource management, improves the decision support and strategic planning capabilities, simplifies cross-department communication and reporting, and strengthens security and compliance. These improvements not only solve the complex resource management challenges in large-scale enterprise environments, but also bring significant value enhancement to users, especially in scenarios that require fine management and high collaboration.

[0044] It is not difficult to understand that, in addition to grouping Pods in Kubernetes cluster resources, the Kubernetes cluster resource grouping module 1 can also be used to group resources such as Services and Namespaces, and even group resources of different types but with the same characteristics into the same group. For example, Pods, Services, and Controllers belonging to the same application can be grouped into the same group.

[0045] In this embodiment, the Kubernetes cluster resource monitoring module 2 allows users to implement customized monitoring strategies for the Kubernetes cluster resources in each group based on the grouping. Users can choose to focus on specific types of indicators (such as CPU usage, memory consumption, network traffic, etc.) according to different business scenarios or role requirements, and set threshold alarm mechanisms. This refined monitoring method not only enhances the effectiveness of monitoring, but also enables key performance issues to be discovered and handled in a timely manner, ensuring the stable operation of the system.

[0046] For example, Figure 4 As shown, in a feasible implementation, the Kubernetes cluster resource monitoring module 2 includes: The Pod monitoring unit 21 is used to monitor the Pods in the Kubernetes cluster resources and output the Pod monitoring results, wherein the Pod monitoring results include the monitoring results of at least one Pod; Kubernetes cluster resource monitoring results include Pod monitoring results.

[0047] In this embodiment, the Kubernetes cluster resource monitoring module 2 includes a Pod monitoring unit 21 specifically used to monitor Kubernetes cluster resources such as Pods, so that users can perform required monitoring of Pods in Kubernetes cluster resources through the Pod monitoring unit 21, such as monitoring the running status, resource usage, throughput, error rate, etc. of the Pods.

[0048] It is not difficult to understand that when the Pod monitoring unit 21 monitors that a Pod that is classified into a specific service group is deleted, the service grouping unit 11 can be notified to update the specific service group. Correspondingly, when the Pod monitoring unit 21 monitors that a new Pod is created, the service grouping unit 11 can also be notified to group the Pod.

[0049] It is understandable that when a new Pod is created, the service grouping unit 11 can determine which Service in the Kubernetes cluster resources it belongs to based on the label of the Pod, thereby dividing the Pod into the corresponding service group (a group of Pods logically defined by a Service usually has the same business logic and implements the same functions, that is, a specific Service usually corresponds to a specific microservice).

[0050] Furthermore, in a feasible implementation manner, the Pod monitoring unit 21 is also used for: When receiving a monitoring instruction for a target Pod, monitor the target Pod and output a monitoring result of the target Pod, wherein the monitoring result of the target Pod is a monitoring result of the target Pod; When receiving a monitoring instruction for a target service group, monitor the target service group and output a monitoring result of the target service group, wherein the monitoring result of the target service group includes monitoring results of all Pods in the target service group; In case of receiving a monitoring instruction for a target application group, monitoring the target application group and outputting a monitoring result of the target application group, wherein the monitoring result of the target application group includes monitoring results of all service groups in the target application group; The Pod monitoring result includes at least one of a target Pod monitoring result, a target service group monitoring result, and a target application group monitoring result.

[0051] It should be noted that the target Pod is a specific Pod in the Kubernetes cluster resources, the target service group is a specific service group in the service grouping result, and the target application group is a specific application group in the application grouping result.

[0052] In this embodiment, the user can specify a Pod in the Kubernetes cluster resources as a target Pod through the Pod monitoring unit 21, so as to perform targeted monitoring on the target Pod. Accordingly, when the user needs to view and monitor a certain service group or application group, the service group can also be specified as the target service group, or the application group can be specified as the target application group, so as to perform targeted monitoring.

[0053] In addition, the Pod monitoring unit 21 can also be used to monitor a Pod in the Kubernetes cluster resources regularly or in real time, or a service group in the service grouping results, or an application group in the application grouping results, or even a project group in the project grouping results, and a department group in the department grouping results. Specifically, the user or the system can pre-set a monitoring plan for a Pod or group, so that the Pod monitoring unit 21 executes the monitoring plan and monitors the Pod or group regularly or in real time.

[0054] It should be noted that, in this embodiment, monitoring a certain group is essentially monitoring each member in the group to obtain the monitoring results of each member, and then the overall situation of the group can be analyzed based on the monitoring results of each member. For example, the operating status of each member can be monitored, and then the operating status of the group as a whole can be determined based on the operating status of each member.

[0055] It is understandable that if Figure 5 As shown, in this embodiment, in addition to the Pod monitoring unit 21, the Kubernetes cluster resource monitoring module 2 may also include a Service monitoring unit 22 specifically used to monitor a type of Kubernetes cluster resource, such as Service, a Controller monitoring unit 23 specifically used to monitor a type of Kubernetes cluster resource, such as Controller, etc. This embodiment does not make any specific limitations on this.

[0056] In this embodiment, the Kubernetes cluster resource visualization module 3 combines the Kubernetes cluster resource grouping results output by the Kubernetes cluster resource grouping module 1 and the Kubernetes cluster resource monitoring results output by the Kubernetes cluster resource monitoring module 2 to provide users with an intuitive and interactive visualization display method.

[0057] Specifically, when the user wants to visualize a specific group, the system can generate a monitoring instruction for the specific group, thereby calling the Kubernetes cluster resource monitoring module 2 to monitor the Kubernetes cluster resources corresponding to the specific group, obtain the corresponding monitoring results, and then visualize the specific group based on the monitoring results.

[0058] Exemplarily, in a feasible implementation, the Kubernetes cluster resource visualization module 3 is further used to: When receiving a visualization display instruction for the target service group, visually display the target service group according to the monitoring result of the target service group; When a visualization display instruction for a target application group is received, the target application group is visualized according to the monitoring result of the target application group.

[0059] In this embodiment, when the user wants to visualize a service group, the service group can be specified as a target service group through a visualization instruction, so that the Kubernetes cluster resource visualization module 3 obtains the monitoring results of the target service group and visualizes the target service group based on the monitoring results.

[0060] Accordingly, when the user wants to visualize a certain application group, the application group can be specified as the target application group through the visualization instruction, so that the Kubernetes cluster resource visualization module 3 obtains the monitoring result of the target application group and visualizes the target application group according to the monitoring result.

[0061] It is not difficult to understand that when a user wishes to visualize a certain project group, the user can also use means similar to the above to achieve a visualized display of the project group.

[0062] It is worth mentioning that, in the present embodiment, the visualization display may be visualized in the form of a topology relationship diagram, wherein the topology relationship diagram is a static topology relationship diagram or a dynamic topology relationship diagram.

[0063] Those skilled in the art will know that a static topology diagram shows a fixed snapshot of Kubernetes cluster resources at a certain moment and will not be updated over time. A dynamic topology diagram can reflect the current status of Kubernetes cluster resources in real time and automatically adjust as resources (such as Pods) are created, deleted, or migrated.

[0064] In this embodiment, when the user visualizes specific resources or groups (such as department groups), the user can set a specific visualization method in the visualization instruction, such as visualization through a static topology diagram or a dynamic topology diagram.

[0065] It is not difficult to understand that when a dynamic topology diagram is used for visualization, the system will monitor the resources involved in the dynamic topology diagram regularly or in real time through the Kubernetes cluster resource monitoring module 2, so as to update the dynamic topology diagram in time when the monitoring results change.

[0066] It should also be noted that, in this embodiment, the visualization display instructions can be subdivided into two categories. The first category is used to create a new topology relationship diagram for visualization display, and the second category is to perform visualization display based on the current topology relationship diagram.

[0067] Among them, the second type of visual display instructions are only applicable to groups that already have corresponding topological nodes in the current topological relationship diagram, but whose members have not yet been expanded to display. For example, service group A consists of Pod1, Pod2, and Pod3. In the current topological relationship diagram, there is a topological node corresponding to service group A, but there are no topological nodes corresponding to Pod1, Pod2, and Pod3 under service group A. Then, the second type of visual display instructions can be used to expand the service group A, thereby generating topological nodes corresponding to Pod1, Pod2, and Pod3 in the current topological relationship diagram, and obtaining a new topological relationship diagram.

[0068] Through the second type of visualization display instructions, this embodiment can load the corresponding resource data for visualization when the user needs to expand a certain group, without having to load and display all the resource data into the topology diagram from the beginning, which greatly improves the smoothness of loading and displaying the visualization interface.

[0069] Furthermore, in a feasible implementation manner, the Kubernetes cluster resource visualization module 3 is also used to: When receiving a folding instruction for the target service group, folding the target service group in the topology relationship graph; When a folding instruction for a target application group is received, the target application group is folded in the topology relationship graph.

[0070] In this embodiment, the expanded groups can be folded again through corresponding folding instructions, thereby hiding the parts that the user is not currently concerned about, reducing visual clutter, making the visual interface neater, and allowing users to focus on the content they are concerned about.

[0071] This implementation supports folding and expanding operations on the topological relationship diagram, so that you can start with a high-level overview, gradually expand the groups of interest as the exploration deepens, and hide unnecessary content.

[0072] Further, in a feasible implementation manner, the monitoring result includes a result of monitoring the operating status, and the visual display includes visualization of the operating status.

[0073] In this embodiment, the monitoring of Kubernetes cluster resources by the Kubernetes cluster resource monitoring module 2 includes monitoring of the running status. Accordingly, when performing a visual display, the running status of each group or cluster resource can be displayed.

[0074] Taking Pod as an example, there are five running states: Pending, Running, Succeeded, Failed, and Unknown, corresponding to the five life cycle stages of Pod. If the running state of a Pod is Failed, the monitoring result of the running state of the Pod is determined to be abnormal (otherwise it is normal). At this time, the running state of the Pod can be reflected in the topological node corresponding to the Pod in the topological relationship diagram through text, color, icon, etc., so that users can see the running state of the Pod at a glance after seeing the topological relationship diagram.

[0075] In addition, it should be noted that for each group, the monitoring result of its operating status depends on the monitoring result of the operating status of its members in the group. For example, service group A includes Pod1, Pod2 and Pod3. As long as the monitoring result of the operating status of any one of these three Pods is abnormal, the monitoring result of the operating status of service group A is abnormal.

[0076] In a feasible implementation manner, the icon of each topological node in the topological relationship diagram allows for custom settings.

[0077] In this embodiment, the user can customize the icons of each topological node in the topological relationship diagram. Specifically, when the Kubernetes cluster resources are grouped by the Kubernetes cluster resource grouping module 1, the visualization icons corresponding to each group can be set, so that when the visualization is performed by the topological relationship diagram, the visualization icons corresponding to each group are referred to for visualization.

[0078] Through this implementation, users can select unique icons for different types of resources (such as Pods, services, namespaces, etc.) or specific application groups, making these elements easier to identify in complex topology diagrams, helping users to understand and remember the structure of the system more quickly, thereby improving work efficiency and personal satisfaction.

[0079] It is understandable that in this embodiment, the user can view detailed information (ie, monitoring results) of each topological node in the topological relationship diagram. For example, the user can right-click a topological node to open the detailed information of the topological node for viewing.

[0080] It should be noted that, in this embodiment, a special database can be set up to store and maintain the Kubernetes cluster resource grouping results and the Kubernetes cluster resource monitoring results, ensuring that the Kubernetes cluster resource visualization module 3 always visualizes the Kubernetes cluster resources based on the latest Kubernetes cluster resource grouping results and the Kubernetes cluster resource monitoring results. That is, in a feasible implementation, each grouping management operation of the Kubernetes cluster resource grouping module 1 will correspond to the update of the Kubernetes cluster resource grouping results in the database, and accordingly, each monitoring operation of the Kubernetes cluster resource monitoring module 2 will correspond to the update of the Kubernetes cluster resource monitoring results in the database, and each visualization display operation of the Kubernetes cluster resource visualization module 3 is implemented based on the Kubernetes cluster resource grouping results and the Kubernetes cluster resource monitoring results stored in the database.

[0081] Through the database, this embodiment can decouple the visualization of cluster resources from grouping and monitoring, so that each module can focus on its own task without having to care about other modules.

[0082] It can be understood that in this embodiment, in addition to the grouping function, the Kubernetes cluster resource grouping module 1 also has functions such as creating, managing, updating and deleting groups.

[0083] In this embodiment, the Kubernetes cluster resource visualization module 3 presents the overall health status of the cluster, the relationship between resource groups and their dynamic change trends in a graphical interface, helping users to quickly understand the complex cluster environment.

[0084] Through the mutual cooperation of the above modules in the Kubernetes cluster resource visualization system 100, this embodiment effectively solves the technical problem of insufficient practicality of visualization of Kubernetes cluster resources in related technologies, ensuring that users can select the visualization display of Kubernetes cluster resources corresponding to the required grouping in a specific direction according to their actual needs.

[0085] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A Kubernetes cluster resource visualization system, characterized in that: The system comprises: A Kubernetes cluster resource grouping module, used to group the Kubernetes cluster resources and output the Kubernetes cluster resource grouping results; A Kubernetes cluster resource monitoring module, used to monitor the Kubernetes cluster resources and output Kubernetes cluster resource monitoring results; The Kubernetes cluster resource visualization module is used to visualize the Kubernetes cluster resources according to the Kubernetes cluster resource grouping results and the Kubernetes cluster resource monitoring results.

2. The Kubernetes cluster resource visualization system according to claim 1, characterized in that: The Kubernetes cluster resource grouping module includes: A service grouping unit, configured to group the Pods in the Kubernetes cluster resources to obtain a service grouping result, wherein the service grouping result includes at least one service group, and the service group includes at least one Pod; an application grouping unit, configured to group the service groups in the service grouping result to obtain an application grouping result, wherein the application grouping result includes at least one application group, and the application group includes at least one service group; The Kubernetes cluster resource grouping result includes the service grouping result and the application grouping result.

3. The Kubernetes cluster resource visualization system according to claim 2, characterized in that: The Kubernetes cluster resource grouping module also includes: A project grouping unit, configured to group the application groups in the application grouping result to obtain a project grouping result, wherein the project grouping result includes at least one project grouping, and the project grouping includes at least one application grouping; A department grouping unit, used for grouping the project groups in the litigation project grouping result to obtain a department grouping result, wherein the department grouping result includes at least one department grouping, and the department grouping includes at least one project grouping; The Kubernetes cluster resource grouping results include the service grouping results, the application grouping results, the project grouping results and the department grouping results.

4. The Kubernetes cluster resource visualization system according to claim 3, characterized in that: The Kubernetes cluster resource monitoring module includes: A Pod monitoring unit, configured to monitor the Pods in the Kubernetes cluster resources and output Pod monitoring results, wherein the Pod monitoring results include monitoring results of at least one Pod; The Kubernetes cluster resource monitoring results include the Pod monitoring results.

5. The Kubernetes cluster resource visualization system according to claim 4, characterized in that: The Pod monitoring unit is also used to: When receiving a monitoring instruction for a target Pod, monitor the target Pod and output a target Pod monitoring result, wherein the target Pod monitoring result is a monitoring result of the target Pod; In case of receiving a monitoring instruction for a target service group, monitoring the target service group and outputting a monitoring result of the target service group, wherein the monitoring result of the target service group includes monitoring results of all Pods in the target service group; In case of receiving a monitoring instruction for a target application group, monitoring the target application group and outputting a monitoring result of the target application group, wherein the monitoring result of the target application group includes monitoring results of all service groups in the target application group; The Pod monitoring result includes at least one of the target Pod monitoring result, the target service group monitoring result and the target application group monitoring result.

6. The Kubernetes cluster resource visualization system according to claim 5, characterized in that: The Kubernetes cluster resource visualization module is also used to: When receiving a visual display instruction for a target service group, visually display the target service group according to the monitoring result of the target service group; When a visual display instruction for a target application group is received, the target application group is visually displayed according to the monitoring result of the target application group.

7. The Kubernetes cluster resource visualization system according to claim 6, characterized in that: The visualization display is visualized in the form of a topology relationship diagram, wherein the topology relationship diagram is a static topology relationship diagram or a dynamic topology relationship diagram.

8. The Kubernetes cluster resource visualization system according to claim 7, characterized in that: The Kubernetes cluster resource visualization module is also used to: When receiving a folding instruction for a target service group, folding the target service group in the topology relationship graph; In case of receiving a folding instruction for a target application group, the target application group is folded in the topology relationship graph.

9. The Kubernetes cluster resource visualization system according to claim 8, characterized in that: The monitoring result includes the result of monitoring the running status, and the visualization includes the visualization of the running status.

10. The Kubernetes cluster resource visualization system according to claim 9, characterized in that: The icons of each topological node in the topological relationship diagram allow for custom settings.

Images