CN116909680A - Method for entering Pod container in container arranging system cluster - Google Patents
Method for entering Pod container in container arranging system cluster Download PDFInfo
- Publication number
- CN116909680A CN116909680A CN202310666541.7A CN202310666541A CN116909680A CN 116909680 A CN116909680 A CN 116909680A CN 202310666541 A CN202310666541 A CN 202310666541A CN 116909680 A CN116909680 A CN 116909680A
- Authority
- CN
- China
- Prior art keywords
- pod
- container
- entering
- information
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000012544 monitoring process Methods 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 3
- 238000007726 management method Methods 0.000 description 4
- 238000012550 audit Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45579—I/O management, e.g. providing access to device drivers or storage
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method for entering Pod containers in a container arranging system cluster, which comprises the following steps: acquiring Pod resource information of a target container arranging system cluster; obtaining Pod container information corresponding to each Pod container according to the Pod resource message, and registering the Pod container information in a local system to obtain a container asset record list; and when an entering instruction is received, determining target Pod container information in the container asset record list according to the entering instruction, and entering a corresponding Pod container according to the target Pod container information. According to the invention, the container asset record list is obtained by registering in the local system according to the obtained Pod resource message, and after receiving the entering instruction, the target Pod container information in the asset record list can be determined and the target Pod container information can be entered into the corresponding Pod container, so that the Pod container entering the Pod arranging system cluster conveniently and rapidly is realized.
Description
Technical Field
The invention relates to the technical field of cloud services, in particular to a method for entering a Pod container in a container arrangement system cluster.
Background
Currently, with the popularity of container orchestration system clusters, container service orchestration on the cloud using the container orchestration system clusters has become an implementation standard for native deployment of the cloud. Behind a large business system, backend services may consist of hundreds or thousands or even more micro-service containers that are uniformly deployed within a cluster of container orchestration systems.
With the increase of the number of containers, the online access to Pod containers for debugging and troubleshooting problems can become very difficult for numerous container service units. A common approach to entering Pod containers is to program the system cluster command line tool kubectl into Pod containers through native containers. This method generally requires that the complete container ID value be obtained by passing the get ports command of kubecl (the Pod ID value usually varies with the life cycle of the container and has a long hash code value, which is difficult to memorize), then the command line is used to transfer the Pod ID value, and some other necessary parameters are taken to access the container. Such a method is inconvenient to operate into Pod containers.
Accordingly, the prior art has drawbacks and needs to be improved and developed.
Disclosure of Invention
The invention aims to solve the technical problem that the entering operation of the Pod container in the container arranging system cluster is inconvenient.
The technical scheme adopted for solving the technical problems is as follows:
a method of entering Pod containers in a cluster of container orchestration systems, the method comprising:
acquiring Pod resource information of a target container arranging system cluster;
obtaining Pod container information corresponding to each Pod container according to the Pod resource message, and registering the Pod container information in a local system to obtain a container asset record list;
and when an entering instruction is received, determining target Pod container information in the container asset record list according to the entering instruction, and entering a corresponding Pod container according to the target Pod container information.
In one implementation, the acquiring the Pod resource message of the target container orchestration system cluster includes:
an interface for connecting the target container orchestration system cluster in a long connection;
and monitoring the interface of the target container arranging system cluster to obtain the Pod resource message of the target container arranging system cluster.
In one implementation, the Pod resource message includes a Pod IP value, a Pod name, and an event type.
In one implementation manner, the obtaining Pod container information corresponding to each Pod container according to the Pod resource message, registering the Pod container information in a local system, and obtaining a container asset record list includes:
extracting the Pod IP value and the Pod name in the Pod resource message to obtain Pod container information corresponding to each Pod container;
when the event type is newly established, setting the Pod IP value as an initial IP value, and registering the initial IP value and the Pod name in a local system to obtain a container asset record list.
In one implementation manner, the obtaining Pod container information corresponding to each Pod container according to the Pod resource message, registering the Pod container information in a local system, and obtaining a container asset record list, further includes:
when the event type is updated, searching Pod container information corresponding to the Pod name according to the Pod name, updating the initial IP value in the Pod container information to the Pod IP value, and obtaining an updated container asset record list;
and when the event type is deleting, searching corresponding Pod container information according to the Pod name and the Pod IP value, and deleting the Pod container information to obtain an updated container asset record list.
In one implementation, when receiving an entry instruction, determining target Pod container information in the container asset record list according to the entry instruction, and entering a corresponding Pod container according to the target Pod container information, where the determining includes:
automatically generating a unique digital index sequence number for each Pod container information in the container asset record list in advance;
when an entering instruction is received, determining a target digital index sequence number according to the entering instruction;
searching target Pod container information in the container asset record list according to the target digital index serial number;
and entering a corresponding Pod container according to the target Pod container information.
In one implementation manner, when receiving the entry instruction, determining the target Pod container information in the container asset record list according to the entry instruction, and entering the corresponding Pod container according to the target Pod container information, further includes:
recording all operation information and returned result information after entering the Pod container, and storing the operation information and the returned result information as a history record.
The invention also provides an access device for Pod containers in a cluster of container arranging systems, which comprises:
the message acquisition module is used for acquiring Pod resource messages of the target container arranging system cluster;
the registration module is used for obtaining Pod container information corresponding to each Pod container according to the Pod resource message, registering the Pod container information in a local system and obtaining a container asset record list;
and the entering module is used for determining target Pod container information in the container asset record list according to the entering instruction when receiving the entering instruction, and entering a corresponding Pod container according to the target Pod container information.
The invention also provides a terminal, comprising: the method comprises the steps of a memory, a processor and an entering program of a Pod container in a Pod arrangement system cluster, wherein the entering program of the Pod container in the Pod arrangement system cluster is stored in the memory and can run on the processor, and the entering method of the Pod container in the Pod arrangement system cluster is realized when the entering program of the Pod container in the Pod arrangement system cluster is executed by the processor.
The invention also provides a computer readable storage medium storing a computer program executable for implementing the steps of the method of entering Pod containers in a cluster of container orchestration systems as described above.
The invention provides a method for entering Pod containers in a container arranging system cluster, which comprises the following steps: acquiring Pod resource information of a target container arranging system cluster; obtaining Pod container information corresponding to each Pod container according to the Pod resource message, and registering the Pod container information in a local system to obtain a container asset record list; and when an entering instruction is received, determining target Pod container information in the container asset record list according to the entering instruction, and entering a corresponding Pod container according to the target Pod container information. According to the invention, the container asset record list is obtained by registering in the local system according to the obtained Pod resource message, and after receiving the entering instruction, the target Pod container information in the asset record list can be determined and the target Pod container information can be entered into the corresponding Pod container, so that the Pod container entering the Pod arranging system cluster conveniently and rapidly is realized.
Drawings
FIG. 1 is a flow chart of a preferred embodiment of a method for entering Pod containers in a cluster of container orchestration systems according to the present invention.
Fig. 2 is a flowchart showing an implementation of the method for entering Pod containers in the Pod arrangement system cluster according to the present invention.
Fig. 3 is a functional block diagram of a preferred embodiment of an access device for Pod containers in a cluster of container orchestration systems according to the present invention.
Fig. 4 is a functional block diagram of a preferred embodiment of the terminal of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more clear and clear, the present invention will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
The following problems also exist with the native container orchestration system cluster command line tool kubectl entering the Pod container:
1. the pre-conditions required for entering the Pod container are more, a docker or kubectl command line tool and a key for connecting the clusters are required to be additionally used, and an operator needs to have the operation authority of an administrator;
2. the authority entering the Pod container cannot be finely distributed, and the role-based access control authority management of the container arrangement system cluster can only be accurate to the space name level, if the authority of a plurality of business service modules entering the Pod container under the same space name is distributed to different users, the requirements cannot be met;
3. the audit is inconvenient, which commands are executed after entering the container, and the commands cannot be recorded and stored in a centralized way.
According to the invention, when the resource type in a monitoring container arrangement system (Kubernetes) cluster is Pod and the event type is newly built, deleted or updated, the Pod name and Pod IP value in the event are extracted in real time, and the call to an open-source fort system (Jumpserver) interface is made according to different event types. The event notification linkage mechanism of the container arrangement system cluster and the open source fort system is realized, so that the capacity of dynamically registering or removing Pod container connection information of the container arrangement system cluster to the open source fort system in real time is realized, pod container connection information in the container arrangement system cluster is synchronized to the open source fort system in real time, the open source fort system has a container list required by logging in a container, and an end user can view the container list, select and enter the container directly through the open source fort system. The method greatly simplifies the complicated step of entering the container by the cluster of the container arrangement system, does not need to additionally use a docker open source containerization platform or kubectl command line tool and a key for connecting the cluster, and an operator needs to have the operation authority of an administrator, so that the authority for entering the Pod container can be finely distributed, all operation information and return information after entering the Pod container are supported to be recorded, and the audit is convenient.
Referring to fig. 1, the method for entering Pod containers in the container arranging system cluster according to the embodiment of the present invention includes the following steps:
step S100, obtaining Pod resource information of the target container arranging system cluster.
In one implementation, the fort obtains the Pod resource message of the target container orchestration system cluster. Specifically, the fort machine is connected with a target container arranging system cluster interface and monitors and acquires Pod resource messages of the target container arranging system cluster. In another implementation manner, other devices are connected with the target container arranging system cluster interface, the Pod resource message of the target container arranging system cluster is monitored and obtained, and then the device obtains Pod container information corresponding to each Pod container according to the Pod resource message, and then the Pod container information is transmitted to the fort machine.
In one implementation, the step S100 specifically includes:
step S110, connecting the interfaces of the target container arranging system cluster in a long connection mode;
and step S120, monitoring an interface of the target container arranging system cluster to obtain a Pod resource message of the target container arranging system cluster.
Specifically, the monitoring the interface of the target container arranging system cluster includes: monitoring an interface of the target container arranging system cluster, and receiving various event information returned by the interface in the monitoring process; the obtaining the Pod resource message of the target container arranging system cluster includes: and screening the event message with the Pod resource type to obtain the Pod resource message of the target container arranging system cluster. The interface of the target container arranging system cluster is connected in a long connection mode, so that the resource information of the target container arranging system cluster can be obtained in real time and screened, and the purpose of efficiently obtaining the Pod resource information of the target container arranging system cluster is achieved.
In one implementation, the Pod resource message includes a Pod IP value, a Pod name, and an event type.
As shown in fig. 1, the method for entering Pod containers in the container arranging system cluster further includes the following steps:
and step 200, obtaining Pod container information corresponding to each Pod container according to the Pod resource message, and registering the Pod container information in a local system to obtain a container asset record list.
Specifically, the Pod resource message includes resource messages of all Pod containers in the container orchestration system cluster. The local system in the bastion machine is a bastion machine system, specifically, an active bastion machine system is configured in the bastion machine, and each Pod container information is registered in the active bastion machine system to obtain a container asset record list. The open source fort machine system is a JumpServer. According to the invention, through monitoring the interfaces of the target container arranging system cluster, the information of each Pod container is obtained and registered in the local system, so that a container asset record list is obtained, and the data integrity of the container asset record list is effectively ensured.
In one implementation, the step S200 specifically includes:
step S210, extracting the Pod IP value and the Pod name in the Pod resource message to obtain Pod container information corresponding to each Pod container;
and step S220, when the event type is newly established, setting the Pod IP value as an initial IP value, and registering the initial IP value and the Pod name in a local system to obtain a container asset record list.
Specifically, after the Pod resource message is acquired, extracting a Pod IP value and a Pod name in the Pod resource message to obtain Pod container information corresponding to each Pod container. The extracted Pod IP value is used as the Pod IP value for registering the Pod container to the open source fort system; the extracted Pod name is used as the Pod name finally registered to the open source fort system. The event type in the Pod resource message is extracted, the event type in the resource message of each Pod container is judged, and when the event type is newly built, the Pod in the container arrangement system is not allocated to the IP under the condition that the initialization is not completely created, so that a fixed initial IP value needs to be temporarily designated in order to create a record in the fort machine. The Pod IP value is set to an initial IP value, which is 9.9.9.9. Transmitting the initial IP value and the Pod name of each Pod container in the container arrangement system to an API/assets/add interface of the open source fort system for registration, and obtaining a container asset record list after registration is completed. The registration of the Pod container in the bastion machine is realized in the mode, no extra container arrangement system cluster CLI, docker CLI or other cluster management tools are needed, and higher manager authority is not needed, so that the Pod container can be operated by the authorized bastion machine user and the related service module authority, and the operation is convenient and quick.
In one implementation, after the step S200, the method further includes:
when the event type is updated, searching Pod container information corresponding to the Pod name according to the Pod name, updating the initial IP value in the Pod container information to the Pod IP value, and obtaining an updated container asset record list;
and when the event type is deleting, searching corresponding Pod container information according to the Pod name and the Pod IP value, and deleting the Pod container information to obtain an updated container asset record list.
Specifically, when the event type is updated, as each Pod container is successfully registered in the local system, the Pod container information corresponding to the Pod Name is searched according to the Pod Name, and an open source fort system API/assets/update interface is called to update the IP corresponding to the record named Pod Name field value in the open source fort system to the Pod IP value in the event, at this time, the initial IP 9.9.9.9 pre-allocated in the fort machine in the new creation stage is updated to the final Pod IP, and the login can be performed through the fort machine. When the event type is deleting, the Pod name and the Pod IP value search corresponding Pod container information, and call an API/assets/delete interface of the system of the bastion machine to delete the corresponding container asset record on the bastion machine, and at the moment, the container asset record in the bastion machine is deleted. The invention updates and deletes the container asset record list by directly calling the interface of the open source fort system, simplifies the operation flow, improves the operation efficiency and improves the safety and the reliability.
As shown in fig. 1, the method for entering Pod containers in the container arranging system cluster further includes the following steps:
and step S300, when an entering instruction is received, determining target Pod container information in the container asset record list according to the entering instruction, and entering a corresponding Pod container according to the target Pod container information.
Specifically, the target Pod container information may be determined according to an entry instruction. The entry instruction may be issued by an authorized bastion user. The distribution of the open source fort system can control the user to see the authority of the container list, the authority of entering the container and the validity period of the corresponding authority, distribute the authority for the user according to the service module, refine the authority of entering the Pod container, and avoid the problem that the authority management of the container arranging system cluster based on the role access control can only be accurate to the space name level, if the authority of entering the Pod container by a plurality of service modules under the same space name is distributed to different users, the requirement can not be met.
In one implementation, the step S300 specifically includes:
step S310, automatically generating a unique digital index sequence number for each piece of Pod container information in the container asset record list in advance;
step S320, when an entering instruction is received, determining a target digital index sequence number according to the entering instruction;
step S330, searching target Pod container information in the container asset record list according to the target digital index sequence number;
and step S340, entering a corresponding Pod container according to the target Pod container information.
Specifically, a unique numerical index number, such as 1, 2, 3, etc., is automatically generated in advance for each Pod container information in the container asset record list. The user can check the list of the container list after logging in the fort terminal through the secure shell protocol. If the list of the container list is ID 1Name: container-847 f76cb58-cdnwj IP 192.168.1.12, ID 2Name: container-756c778967-z7282IP 192.168.1.13, ID 3Name: container-65d7d6ff9c-dhn IP 192.168.1.14. The user can enter the corresponding container by only inputting the numerical index number 2. The random container names which are difficult to memorize do not need to be input, the flow is greatly simplified, and the entering of the container is more convenient, quicker and interactive.
In one implementation, before the step S320, the method further includes:
and receiving a keyword searching instruction sent by a user, determining a keyword according to the keyword searching instruction, and determining Pod container information and a digital index serial number corresponding to the keyword in the container asset record list.
Specifically, since the Pod container name is long and contains a complex hash value, keywords of the name can be input to filter the container list, and the container list and the numerical index number corresponding to the keywords are checked.
In one implementation, after the step S340, the method further includes:
recording all operation information and returned result information after entering the Pod container, and storing the operation information and the returned result information as a history record.
Specifically, the fort machine records all operation information and returned result information after entering the Pod container, saves the operation information and the returned result information as a history record, supports a user to track the history, supports playback of all operations in a video recording mode, and facilitates user auditing.
In one implementation, as shown in FIG. 2, the open source fort system includes a message acquisition module and a registration module. The method for entering the Pod container in the container arranging system cluster comprises the following specific implementation flow:
a1, connecting a container arranging system cluster interface;
a2, monitoring the interface by using a message acquisition module;
step A3, judging whether the resource type is Pod; if yes, executing the step A4, and if not, ending;
step A4, transmitting the Pod resource message to a registration module;
step A5, judging the event type; if the event type is new, executing the step A6, if the event type is updated, executing the step A7, and if the event type is deleted, executing the step A8;
step A6, the event type is newly built, and a corresponding interface of the system of the open source fort is called to register a user;
step A7, the event type is updated, and a corresponding interface of the system of the open source fort is called to update the Pod IP value;
step A8, the event type is deleting, and a corresponding interface of the system of the open source fort machine is called to delete the Pod container information;
step A9, receiving an entering instruction of a authorized bastion machine user;
and step A10, entering a Pod container in the container arranging system cluster according to the container record list.
The method can quickly open the event notification linkage of the container arranging system cluster and the open source fort machine system. Because the open source fort system is mature in the industry and has good functions of asset management, authority allocation, log audit and the like, the container login operation can be realized by the existing capability of the open source fort system very fast and convenient. Meanwhile, the container arrangement system cluster is not invaded at all, and the existing cluster is not required to be modified, so that the container arrangement system cluster is formed by expanding the message acquisition module and the registration module.
In an implementation manner, as shown in fig. 3, based on the method for entering a Pod container in the Pod arranging system cluster, the invention further correspondingly provides an entering device of the Pod container in the Pod arranging system cluster, which includes:
a message obtaining module 100, configured to obtain a Pod resource message of the target container arranging system cluster;
the registration module 200 is configured to obtain Pod container information corresponding to each Pod container according to the Pod resource message, and register the Pod container information in a local system to obtain a container asset record list;
and an entering module 300, configured to determine, when an entering instruction is received, target Pod container information in the container asset record list according to the entering instruction, and enter a corresponding Pod container according to the target Pod container information.
In an implementation manner, the invention further provides a terminal correspondingly, as shown in fig. 4, including: the method comprises the steps of a memory 20, a processor 10 and an entering program 30 of Pod containers in a Pod system cluster stored on the memory 20 and capable of running on the processor 10, wherein the entering program 30 of Pod containers in the Pod system cluster is executed by the processor 10 to realize the steps of the entering method of Pod containers in the Pod system cluster as described above.
The invention also provides a computer readable storage medium storing a computer program executable for implementing the steps of the method of entering Pod containers in a cluster of container orchestration systems as described above.
In summary, the present invention provides a method for entering Pod containers in a container arranging system cluster, where the method includes: acquiring Pod resource information of a target container arranging system cluster; obtaining Pod container information corresponding to each Pod container according to the Pod resource message, and registering the Pod container information in a local system to obtain a container asset record list; and when an entering instruction is received, determining target Pod container information in the container asset record list according to the entering instruction, and entering a corresponding Pod container according to the target Pod container information. According to the invention, the container asset record list is obtained by registering in the local system according to the obtained Pod resource message, and after receiving the entering instruction, the target Pod container information in the asset record list can be determined and the target Pod container information can be entered into the corresponding Pod container, so that the Pod container entering the Pod arranging system cluster conveniently and rapidly is realized.
It is to be understood that the invention is not limited in its application to the examples described above, but is capable of modification and variation in light of the above teachings by those skilled in the art, and that all such modifications and variations are intended to be included within the scope of the appended claims.
Claims (10)
1. A method of accessing Pod containers in a cluster of container orchestration systems, the method comprising:
acquiring Pod resource information of a target container arranging system cluster;
obtaining Pod container information corresponding to each Pod container according to the Pod resource message, and registering the Pod container information in a local system to obtain a container asset record list;
and when an entering instruction is received, determining target Pod container information in the container asset record list according to the entering instruction, and entering a corresponding Pod container according to the target Pod container information.
2. The method of accessing Pod containers in a container orchestration system cluster according to claim 1, wherein the obtaining the Pod resource message of the target container orchestration system cluster comprises:
an interface for connecting the target container orchestration system cluster in a long connection;
and monitoring the interface of the target container arranging system cluster to obtain the Pod resource message of the target container arranging system cluster.
3. The method of claim 1, wherein the Pod resource message comprises a Pod value, a Pod name, and an event type.
4. The method for entering Pod containers in the Pod arrangement system cluster according to claim 3, wherein the obtaining Pod container information corresponding to each Pod container according to the Pod resource message, registering the Pod container information in a local system, and obtaining a container asset record list includes:
extracting the PodIP value and the Pod name in the Pod resource message to obtain Pod container information corresponding to each Pod container;
when the event type is newly established, setting the Pod IP value as an initial IP value, and registering the initial IP value and the Pod name in a local system to obtain a container asset record list.
5. The method for entering Pod containers in the Pod arrangement system cluster according to claim 4, wherein the obtaining Pod container information corresponding to each Pod container according to the Pod resource message, registering the Pod container information in a local system, and obtaining a container asset record list, further comprises:
when the event type is updated, searching Pod container information corresponding to the Pod name according to the Pod name, and updating the initial IP value in the Pod container information to the PodIP value to obtain an updated container asset record list;
and when the event type is deleting, searching corresponding Pod container information according to the Pod name and the Pod IP value, and deleting the Pod container information to obtain an updated container asset record list.
6. The method according to claim 1, wherein when an entry instruction is received, determining target Pod container information in the container asset record list according to the entry instruction, and entering a corresponding Pod container according to the target Pod container information, comprising:
automatically generating a unique digital index sequence number for each Pod container information in the container asset record list in advance;
when an entering instruction is received, determining a target digital index sequence number according to the entering instruction;
searching target Pod container information in the container asset record list according to the target digital index serial number;
and entering a corresponding Pod container according to the target Pod container information.
7. The method according to claim 1, wherein when an entry instruction is received, determining target Pod container information in the container asset record list according to the entry instruction, and entering a corresponding Pod container according to the target Pod container information, further comprising:
recording all operation information and returned result information after entering the Pod container, and storing the operation information and the returned result information as a history record.
8. An access device for Pod containers in a cluster of container orchestration systems, the device comprising:
the message acquisition module is used for acquiring Pod resource messages of the target container arranging system cluster;
the registration module is used for obtaining Pod container information corresponding to each Pod container according to the Pod resource message, registering the Pod container information in a local system and obtaining a container asset record list;
and the entering module is used for determining target Pod container information in the container asset record list according to the entering instruction when receiving the entering instruction, and entering a corresponding Pod container according to the target Pod container information.
9. A terminal, comprising: memory, a processor and an entering program of Pod containers in a Pod orchestration system cluster stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the entering method of Pod containers in a Pod orchestration system cluster according to any one of claims 1-7.
10. A computer readable storage medium, characterized in that it stores a computer program executable for implementing the steps of the method of entering Pod containers in a cluster of container orchestration systems according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310666541.7A CN116909680A (en) | 2023-06-06 | 2023-06-06 | Method for entering Pod container in container arranging system cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310666541.7A CN116909680A (en) | 2023-06-06 | 2023-06-06 | Method for entering Pod container in container arranging system cluster |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116909680A true CN116909680A (en) | 2023-10-20 |
Family
ID=88353898
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310666541.7A Pending CN116909680A (en) | 2023-06-06 | 2023-06-06 | Method for entering Pod container in container arranging system cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116909680A (en) |
-
2023
- 2023-06-06 CN CN202310666541.7A patent/CN116909680A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106528224B (en) | Content updating method, server and system for Docker container | |
| CN109101428B (en) | UI automation test system | |
| CN112214338A (en) | Internet of things cloud platform based on flexible deployment of micro-services | |
| CN111752799A (en) | Service link tracking method, device, equipment and storage medium | |
| CN111277637B (en) | Method, device, terminal and storage medium for merging session groups | |
| CN107688611B (en) | Saltstack-based Redis key value management system and method | |
| CN106294151B (en) | Log test method and device | |
| CN116204438A (en) | Test case generation method, automatic test method and related device | |
| JP7221799B2 (en) | Information processing system and control method for information processing system | |
| CN115328611A (en) | Virtual machine management method, device, server and readable storage medium | |
| CN113792274A (en) | Information management method, management system and storage medium | |
| CN107544894B (en) | Log processing method and device and server | |
| CN109857716B (en) | System interaction log recording method and device, storage medium and server | |
| CN116909680A (en) | Method for entering Pod container in container arranging system cluster | |
| CN114866416A (en) | Multi-cluster unified management system and deployment method | |
| CN112199426B (en) | Interface call management method, device, server and medium under micro-service architecture | |
| CN111368039B (en) | Data management system | |
| CN110413484B (en) | Cluster monitoring method supporting heterogeneous platform | |
| KR20050055240A (en) | Integrated management system for matadata and method thereof | |
| CN109104499B (en) | Session establishing method, device, equipment and storage medium | |
| CN114722261A (en) | Resource processing method and device, electronic equipment and storage medium | |
| CN109684158A (en) | Method for monitoring state, device, equipment and the storage medium of distributed coordination system | |
| CN116684282B (en) | Method and device for initializing newly-added cloud server and computer equipment | |
| CN114756469B (en) | Data relationship analysis method and device and electronic equipment | |
| CN116389172B (en) | Multi-tenant-based container cloud platform resource security management method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |