CN116301943A - Image construction method of kubernetes cluster based on container - Google Patents
Image construction method of kubernetes cluster based on container Download PDFInfo
- Publication number
- CN116301943A CN116301943A CN202310279356.2A CN202310279356A CN116301943A CN 116301943 A CN116301943 A CN 116301943A CN 202310279356 A CN202310279356 A CN 202310279356A CN 116301943 A CN116301943 A CN 116301943A
- Authority
- CN
- China
- Prior art keywords
- image
- container
- configuration file
- application
- mirror image
- 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
- 238000010276 construction Methods 0.000 title claims description 37
- 238000000034 method Methods 0.000 claims abstract description 36
- 238000011161 development Methods 0.000 claims abstract description 35
- 238000012423 maintenance Methods 0.000 claims abstract description 34
- 230000008569 process Effects 0.000 claims description 20
- 230000003068 static effect Effects 0.000 claims description 4
- 230000036541 health Effects 0.000 claims description 3
- 230000001419 dependent effect Effects 0.000 description 6
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 2
- 230000004888 barrier function Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention provides a method for constructing a mirror image of kubernetes cluster based on a container, which comprises the following steps: acquiring a basic image by inheriting image information of a podman container, and constructing an application image of at least one development language based on the basic image; preparing a first configuration file of a podman, wherein the first configuration file comprises a plurality of mirror image warehouses and storage positions of each mirror image warehouse; preparing a second configuration file of at least one development language, wherein the second configuration file comprises a configuration environment on which the at least one development language depends; mounting the catalogs designated by the first configuration file and the second configuration file to a host catalog or distributed shared storage; compiling an operation and maintenance feature configuration file of the application, wherein the operation and maintenance feature configuration file comprises basic operation and maintenance features of the setting application; the CI flow and the CD flow of the application are carried out in an application deployment pipeline to realize deployment in kubernetes clusters.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method for constructing a mirror image of kubernetes cluster based on a container.
Background
Since the Docker container engine is released earlier than the kubernetes container engine, docker itself is not compatible with CRI (when the container is running) interfaces, while Docker authorities do not implement CRI intent, nor do they support some of the new needs of the container, the community wants to get rid of the high maintenance costs of Dockershim. Thus, the kubernetesv1.20 version issues an important change in that the support statement for Docker is directly removed in the following v1.24 version for expiration. Therefore, the original method for constructing the mirror image based on the docker cannot be used after the containerd is replaced, and the mirror image cannot be directly constructed in the kubernetes environment because the containerd has no build command, and tools such as build kit and nerdctl are required to be installed to realize the mirror image construction.
After the current kubernetes replacement container runs as a container, mirror image construction is generally achieved in a way of buildket and nerdctl. Major difficulties or disadvantages: one is to introduce the lack of using materials of two components, and the learning process is difficult; the two additionally introduced tools are greatly different from the original construction tools, so that the use of the tools is hindered.
Therefore, those skilled in the art feel great concern and resistance to the operation of the kubernetes replacement container, so that many people do not want to upgrade a new version of kubernetes, and many new functions cannot be used.
Disclosure of Invention
In order to overcome the technical defects, the invention aims to provide a method for constructing a kubernetes cluster mirror image based on a container to replace the existing container+buildkit+nerdctl mode.
The invention discloses a method for constructing a mirror image of kubernetes cluster based on a container, which comprises the following steps: acquiring a basic image by inheriting image information of a podman container, and constructing an application image of at least one development language based on the basic image; preparing a first configuration file of a podman, wherein the first configuration file comprises a plurality of mirror image warehouses and storage positions of each mirror image warehouse; preparing a second configuration file of at least one development language, wherein the second configuration file comprises a configuration environment on which the at least one development language depends; mounting the catalogs designated by the first configuration file and the second configuration file to a host catalog or distributed shared storage; compiling an operation and maintenance feature configuration file of the application, wherein the operation and maintenance feature configuration file comprises basic operation and maintenance features of the setting application; the CI flow and the CD flow of the application are carried out in an application deployment pipeline to realize deployment in kubernetes clusters.
Preferably, the constructing an application image of at least one development language based on the base image includes: constructing at least one application image based on the base image; and adding compiling environments required by the at least one development language to the at least one application image respectively, and marking the image construction labels.
Preferably, the at least one development language comprises at least one of Java, nodeJs, golang; the compilation environment includes at least one of maven, gradle, noddenpm, go.
Preferably, the plurality of image warehouses includes a domestic image warehouse and a local private image warehouse.
Preferably, the preparing the second configuration file of the at least one development language includes: and configuring the local private warehouse and the domestic warehouse.
Preferably, the basic operation and maintenance features include any one or more of the following: ports, labels, copy numbers, belonging namespaces, health check rules, and exposed service modes.
Preferably, before the CI process and the CD process of the application are performed in the application deployment pipeline, the method further includes: a Jenkinsfile is written to define the steps of the CI process and the CD process.
Preferably, the CI process includes: performing a source code pulling and static code scanning process; matching a compiling environment according to the basic operation and maintenance characteristics to compile, wherein the compiling environment comprises a development language environment and a development framework; completing mirror image construction based on the compiling result, and setting a mirror image name and/or a mirror image identification mark for mirror image pulling; pushing the constructed image to the image repository.
Preferably, the pushing the constructed image to the image warehouse includes: acquiring an access credential of the mirror image warehouse, wherein the access credential comprises an account number and a password; the mirror image is scanned safely and confirmed as safe.
Preferably, the CD process includes: and pulling the image from the image warehouse, and deploying the operation and maintenance feature configuration file into a kubernetes cluster.
After the technical scheme is adopted, compared with the prior art, the method has the following beneficial effects:
1. according to the invention, the process of constructing and pushing the mirror image is realized by introducing the podman container into the container, and the use mode of the podman container is basically consistent with a docker command, so that the learning cost and the use barrier are not increased after the podman is introduced, the operation of a new container can be quickly switched, the learning cost and the use cost are reduced, the fear of a user for upgrading kubernetes is reduced, and the usability and the advancement of the kubernetes serving as an infrastructure are ensured;
2. the scheme of the invention supports multiple languages, and different construction container environments are generated through different tool images, so that the application image construction of the multiple languages is realized, and the corresponding construction environments are selected according to the labels when the application image construction method is used. Three tools are not required to be introduced, so that the integration cost and the learning cost are reduced; and the cache in the container environment is supported, and the construction data cache is realized in the container through the catalog mount, so that the construction time is shortened, and the construction efficiency is improved. Mirror construction of business applications is accomplished in the container by running a construction tool container.
Drawings
Fig. 1 is a flow chart of a mirror image construction method of kubernetes cluster based on a container provided by the invention.
Detailed Description
Advantages of the invention are further illustrated in the following description, taken in conjunction with the accompanying drawings and detailed description.
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in this disclosure to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
In the description of the present invention, it should be understood that the terms "longitudinal," "transverse," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," and the like indicate orientations or positional relationships based on the orientation or positional relationships shown in the drawings, merely to facilitate describing the present invention and simplify the description, and do not indicate or imply that the devices or elements referred to must have a specific orientation, be configured and operated in a specific orientation, and therefore should not be construed as limiting the present invention.
In the description of the present invention, unless otherwise specified and defined, it should be noted that the terms "mounted," "connected," and "coupled" are to be construed broadly, and may be, for example, mechanical or electrical, or may be in communication with each other between two elements, directly or indirectly through intermediaries, as would be understood by those skilled in the art, in view of the specific meaning of the terms described above.
In the following description, suffixes such as "module", "component", or "unit" for representing elements are used only for facilitating the description of the present invention, and are not of specific significance per se. Thus, "module" and "component" may be used in combination.
The container of the present invention is a standardized, stand-alone software package that contains all the necessary elements and can be run anywhere without customization, including application code and supporting libraries. The container is similar to a virtual machine, one process can be virtualized into one container, deployment of applications can be carried, a simple isolation mechanism is provided, and efficient resource utilization and rapid packaging and deployment can be achieved.
The Docker container engine is one of the container engines which are widely used at present, and uses a C/S architecture mode of a Client server (server). The DockerClient is equivalent to a client in a C/S architecture mode and is used for interacting with a user; dockerdaemon acts as a daemon for the Docker container, acting as a server in the C/S architecture mode, for interacting with the DockerClient and managing the Docker image (image) and Docker container (container). Where a Docker image is a template used to create a Docker container, which is an independently running application or set of applications.
Podman, like Docker, is also a container engine, a tool for developing, managing and running containers and container images.
As containerized applications become more complex, developers need tools that can coordinate interactions between containers running on different virtual machines, and even on different physical machines. Such tools are known as container orchestration platforms, and Kubernetes is a type of container orchestration platform. Kubernetes can work with any container that meets the Open Container Initiative (OCI) image specification, which is met by the container of Podman. Kubernetes is an open source for managing containerized applications on multiple hosts in a cloud platform, and the goal of Kubernetes is to make deploying containerized applications simple and efficient, and Kubernetes provides a mechanism for application deployment, planning, updating, and maintenance. Vividly, kubernetes can be understood as a centralized bin integrated vehicle.
The Podman and Docker are compatible overall, due in part to compliance with the open standard, because both engines use containers that conform to the OCI standard, one container can be created with Docker and modified in the Podman, or vice versa, and either container can then be deployed to Kubernetes.
Containerd is an industry standard container, has the advantages of simplicity, robustness, portability and the like, can be operated as a daemon on Linux and window, and is mainly used for managing the complete life cycle of the container on a host system.
Mirror image construction can be understood as making an application into a file identified by a container, including an environment required by the application, while the containerd cannot construct a mirror image, and is biased to be lower (namely, the complete life cycle of the container on the management host system), so that the invention solves the problem that the containerd container mirror image construction cannot be directly constructed after the container is replaced by the containerd in the running process of the containerd container by introducing a podman container in the running process of the containerd container, thereby solving the problem that kubinets cannot directly construct the mirror image after replacing the container in the running process of the container.
Specifically, referring to fig. 1, the invention discloses a method for constructing a mirror image of kubernetes cluster based on a container, which comprises the following steps:
s100, acquiring a basic mirror image by inheriting mirror image information of a podman container, and constructing an application mirror image of at least one development language based on the basic mirror image;
s200, preparing a first configuration file of the podman, wherein the first configuration file comprises a plurality of mirror image warehouses and storage positions of each mirror image warehouse;
s300, preparing a second configuration file of at least one development language, wherein the second configuration file comprises a configuration environment on which the at least one development language depends;
s400, mounting the catalogs designated by the first configuration file and the second configuration file to a host catalog or distributed shared storage;
s500, compiling an operation and maintenance feature configuration file of the application, wherein the operation and maintenance feature configuration file comprises basic operation and maintenance features of the setting application;
s600, performing CI flow and CD flow of the application in an application deployment pipeline to realize deployment in kubernetes clusters.
The solution of the invention can be understood to comprise three main phases: a build tool mirror phase (i.e., building the base tool of the application), a prepare configuration file phase, and an application deployment phase. Wherein step S100 belongs to the build tool mirror phase, S200-S500 belongs to the prepare configuration file phase, and S600 belongs to the application deployment phase.
For step S100, specifically, the method includes: the method comprises the steps of firstly obtaining a basic mirror image by inheriting mirror image information of a podman container, and then constructing at least one application mirror image based on the basic mirror image. For example, a basic mirror image is constructed, and the mirror image information of the podman container is mainly inherited; constructing an image of at least one development language, inheriting a basic image, wherein the at least one development language basically has an environment (such as jre relied on by Java language, net relied on by C# language, etc., which are only examples and not limiting); the required compilation environment is added to the at least one development language and the mirror build tags are marked. According to the steps, we can write a framework dependent environment or at least one development language, when the development language is multiple, so as to realize the mirror image construction foundation of multiple languages in the podman container.
Wherein the at least one development language includes (and is not limited to) at least one of Java, nodeJs, golang; the compilation environment includes at least one of (and is not limited to) maven, gradle, noddenpm, go. Corresponding to the development language and the compiling environment, the labels may be (and are not limited to) maven-jdk8, maven-jdk11, go1.16, nodeJs14, etc.
For step S200, typically, the image repository includes a domestic image repository and a local private image repository. In some cases, the mirror image warehouse further comprises a foreign mirror image warehouse, wherein the domestic mirror image warehouse is faster than the foreign mirror image warehouse in acquiring the mirror image, and the local private mirror image warehouse is faster than the domestic mirror image warehouse, and is mainly used for managing the local mirror image and can also manage the public mirror image outside.
The plurality of mirror image warehouses mainly comprise a domestic mirror image warehouse and a local private mirror image warehouse. Step S200 is mainly to configure the mirror image repository of the podman and the storage location of the mirror image repository, so as to prepare for the subsequent pulling of the mirror image.
For step S300, mainly a configuration environment on which different language frameworks depend is configured, such as a maven source setting. The configuration file is mainly used for configuring a local private warehouse and a domestic warehouse of the dependent environment, and in some cases, can also be used for configuring a foreign warehouse of the dependent environment. For example, the Java's maven source setting.xmal configuration file is a local private mavenom repository and a domestic maven repository for configuring a dependent environment, so as to accelerate the pull speed of the pon dependence. In some embodiments, the local private repository is used preferentially, then the domestic repository, then the foreign repository, to increase the efficiency of obtaining repository files and reduce security risks.
For step S400, since the data will be completely lost after the container is restarted and the reconstruction will take time again, the important application directory is mounted (which can be understood as backup to the local disk or cloud disk) to solve the problem of file data loss in the container after the container is lost and the problem of slow compiling and constructing speed. The method mainly comprises the step S200 of compiling and constructing the catalogs of the base image positions relied by and the catalogs of the configuration environments (such as maven and nodejs local library catalogs) relied by the different language frameworks configured in the step S300, so that the problem that the base image files and the downloaded dependent files can be still shared when a construction container changes is solved, the network consumption is reduced, and the construction efficiency is improved.
Directory mounts may typically be implemented by mounting host directories or distributed shared storage. Wherein, the mounted host catalog has the risk of damage; the distributed shared storage is that the shared storage is performed on a plurality of devices. And a proper catalog mounting mode can be selected according to the requirements.
For step S500, mainly, the basic operation and maintenance features of the application are written, where the basic operation and maintenance features include any one or more of (and are not limited to) the following: ports, labels, copy numbers, belonging namespaces, health check rules, exposure service modes, etc. On the kubernetes platform, the application's operation and maintenance feature profile is a yaml format file.
For step S600, for the final application deployment stage, it is necessary to implement the application CICD flow in the devops application deployment pipeline, and first write the Jenkinsfile to define the steps of the CI flow and the CD flow, further, the Jenkinsfile may define the shell command to be executed, and so on.
Specifically, the CI process includes:
1) Performing a source code pulling and static code scanning process, comprising: setting a code path and branches/tags, and performing source code pulling on a certificate, static code scanning and scanning rule setting;
2) Matching a compiling environment according to the basic operation and maintenance characteristics to compile, wherein the compiling environment comprises a development language environment and a development framework (that is, matching different application basic operation and maintenance characteristics according to different development language environments and development frameworks), and selecting corresponding container labels (such as maven-jdk8 and the like) according to the basic operation and maintenance characteristics (such as names and ports) of the application;
3) And finishing mirror image construction based on the compiling result, namely compiling a dockerfile file (namely setting the dependent environment of application operation and copying the compiled application file to a mirror image), finishing mirror image construction after executing the dockerfile file, and setting a mirror image name and/or a mirror image identification mark for mirror image pulling. Wherein, in some embodiments, the mirror name and/or mirror identification mark may be a display of time plus a random number, without limitation;
4) Pushing the constructed image to an image warehouse, preferably a local private image warehouse; when entering the warehouse, the account number and the password of the warehouse are also needed, and the mirror image is also needed to be scanned safely so as to ensure the safety of the mirror image.
The CD process includes: pulling the mirror image from the mirror image warehouse, and deploying the operation and maintenance feature configuration file into kubernetes clusters, wherein the method specifically comprises the following steps:
1) And writing a common application operation and maintenance feature configuration file app.yaml, wherein in order to use the same template for more applications, the maintenance cost of the template file is reduced, the common parameters in the required extraction application are set as variables, and the common parameters are replaced with specific application basic operation and maintenance features when being specifically executed or used. Finally, storing the file into a file storage service (such as an Arian OSS or a local file server, etc.);
2) Setting pipeline parameter configuration, namely setting specific basic operation and maintenance characteristics of an application when the pipeline is operated (for example, setting an application port number parameter as 8080, setting a name as myapp, and a mirror name as myapp: v1.0, etc.); it should be noted that, the parameter modification may be performed on the operation and maintenance feature configuration file, where the modification may be performed before deployment or during deployment;
3) According to specific application and basic operation and maintenance characteristics, downloading corresponding operation and maintenance characteristic configuration files app.yaml;
4) Setting security credentials of kubernetes clusters, executing app.yaml, if parameters are not replaced at the moment, replacing variables in the app.yaml according to the set parameters, pulling the mirror image from a mirror image warehouse, and starting the mirror image to realize container deployment.
The whole flow of the invention is finished so that one application can run in kubernetes clusters when the container is used as the container, wherein the deployment or mirror image construction is not assisted by using a three-party tool, and the implementation difficulty of replacing the container is greatly reduced.
It should be noted that the embodiments of the present invention are preferred and not limited in any way, and any person skilled in the art may make use of the above-disclosed technical content to change or modify the same into equivalent effective embodiments without departing from the technical scope of the present invention, and any modification or equivalent change and modification of the above-described embodiments according to the technical substance of the present invention still falls within the scope of the technical scope of the present invention.
Claims (10)
1. The image construction method of kubernetes cluster based on the container is characterized by comprising the following steps:
acquiring a basic image by inheriting image information of a podman container, and constructing an application image of at least one development language based on the basic image;
preparing a first configuration file of a podman, wherein the first configuration file comprises a plurality of mirror image warehouses and storage positions of each mirror image warehouse; preparing a second configuration file of at least one development language, wherein the second configuration file comprises a configuration environment on which the at least one development language depends;
mounting the catalogs designated by the first configuration file and the second configuration file to a host catalog or distributed shared storage;
compiling an operation and maintenance feature configuration file of the application, wherein the operation and maintenance feature configuration file comprises basic operation and maintenance features of the setting application;
the CI flow and the CD flow of the application are carried out in an application deployment pipeline to realize deployment in kubernetes clusters.
2. The image construction method of kubernetes cluster based on a container of claim 1, wherein constructing an application image of at least one development language based on the base image comprises:
constructing at least one application image based on the base image;
and adding compiling environments required by the at least one development language to the at least one application image respectively, and marking the image construction labels.
3. The image construction method of a kubernetes cluster based on a con-tainerd container of claim 2, wherein the at least one development language comprises at least one of Java, nodeJs, golang; the compilation environment includes at least one of maven, gradle, noddenpm, go.
4. The image construction method of kubernetes cluster based on a container according to claim 1, wherein the plurality of image repositories includes a domestic image repository and a local private image repository.
5. The method for mirror image construction of a kubernetes cluster based on a con-tainerd container of claim 4, wherein preparing the second configuration file of the at least one development language comprises:
and configuring the local private warehouse and the domestic warehouse.
6. The image construction method of kubernetes cluster based on a container according to claim 1, wherein the basic operation and maintenance features include any one or more of the following: ports, labels, copy numbers, belonging namespaces, health check rules, and exposed service modes.
7. The image construction method of kubernetes cluster based on a container according to claim 1, wherein before the CI flow and the CD flow of the application are performed in the application deployment pipeline, the method further comprises:
a Jenkinsfile is written to define the steps of the CI process and the CD process.
8. The image construction method of kubernetes cluster based on a container according to claim 1 or 7, wherein the CI procedure comprises:
performing a source code pulling and static code scanning process;
matching a compiling environment according to the basic operation and maintenance characteristics to compile, wherein the compiling environment comprises a development language environment and a development framework;
completing mirror image construction based on the compiling result, and setting a mirror image name and/or a mirror image identification mark for mirror image pulling;
pushing the constructed image to the image repository.
9. The image construction method of kubernetes cluster based on a container of claim 8, wherein pushing the constructed image to the image repository comprises:
acquiring an access credential of the mirror image warehouse, wherein the access credential comprises an account number and a password;
the mirror image is scanned safely and confirmed as safe.
10. The image construction method of kubernetes cluster based on a container as claimed in claim 1 or 7, wherein the CD process comprises:
and pulling the image from the image warehouse, and deploying the operation and maintenance feature configuration file into a kubernetes cluster.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310279356.2A CN116301943A (en) | 2023-03-22 | 2023-03-22 | Image construction method of kubernetes cluster based on container |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310279356.2A CN116301943A (en) | 2023-03-22 | 2023-03-22 | Image construction method of kubernetes cluster based on container |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116301943A true CN116301943A (en) | 2023-06-23 |
Family
ID=86788417
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310279356.2A Pending CN116301943A (en) | 2023-03-22 | 2023-03-22 | Image construction method of kubernetes cluster based on container |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116301943A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117112144A (en) * | 2023-09-22 | 2023-11-24 | 上海卓悠网络科技有限公司 | Method and system for deploying k3s on android system and storage medium |
-
2023
- 2023-03-22 CN CN202310279356.2A patent/CN116301943A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117112144A (en) * | 2023-09-22 | 2023-11-24 | 上海卓悠网络科技有限公司 | Method and system for deploying k3s on android system and storage medium |
| CN117112144B (en) * | 2023-09-22 | 2024-03-12 | 上海卓悠网络科技有限公司 | Method and system for deploying k3s on android system and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109947773B (en) | Deploying changes to key patterns in a multi-tenant database system | |
| US7684964B2 (en) | Model and system state synchronization | |
| CN104137065B (en) | Disposed on a client device using XML configuration file and update application and drive formula | |
| US8281012B2 (en) | Managing parallel data processing jobs in grid environments | |
| CN104094256B (en) | Deployment driving or application on the client device with write-in filter | |
| CN101952800B (en) | Accessing different type structures via a common data structure | |
| CN104094226B (en) | Use the application or driving on deployment configuration Automatic Update of File client device | |
| AU2004200639B2 (en) | Integrating design, deployment, and management phases for systems | |
| CN101326489B (en) | OS mini-boot for running multiple environments | |
| CN102567051B (en) | Method and device for preparing graphical installation system of Loongson platform | |
| US9830135B2 (en) | Declarative and pluggable business logic for systems management | |
| US10656971B2 (en) | Agile framework for vertical application development and delivery | |
| US8732692B2 (en) | Deployment and management framework | |
| US10585655B2 (en) | Systems and methods for automated retrofitting of customized code objects | |
| US20150220553A1 (en) | Expandable ad hoc domain specific query for system management | |
| CN102422266A (en) | System and method for building and updating a runtime environment | |
| CN112256278A (en) | Compiling method, device, equipment and storage medium | |
| CN116301943A (en) | Image construction method of kubernetes cluster based on container | |
| CN109634591A (en) | A kind of document handling method and device | |
| CN114461182A (en) | Method and device for pipeline construction, electronic equipment and computer readable storage medium | |
| Demuth et al. | Efficient detection of inconsistencies in a multi-developer engineering environment | |
| CN113127098A (en) | Micro-service architecture-based application program creating method and related equipment | |
| TW200527294A (en) | Versioning support in object-oriented programming languages and tools | |
| Freeman | Essential docker for asp. net Core mvc | |
| CN116601605A (en) | Declaratively provisioning resources on a cloud platform |
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 |