Container Application Template Format for Unified Kubernetes Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Kubernetes does not provide middleware, data-processing frameworks, databases, or cluster storage systems as built-in services, leading to issues with library version conflicts and increased overhead when deploying containerized applications, which can result in unexpected behavior and higher costs due to the need for additional computing resources.
Innovation Solution
A standardized format for containerized applications is introduced, allowing a single parser to deploy different types of applications by defining application information such as name, version, API version, and deployment details, reducing the need for multiple parsers and resource overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If multiple applications are installed on a server with shared libraries, then resource utilization is improved, but library version conflicts cause unexpected behavior
Solution Approach 1:
The patent segments the server environment into isolated container units, where each container encapsulates its own application and library dependencies. This segmentation prevents library version conflicts between applications while maintaining resource efficiency, as each container is a self-contained unit that can share the underlying server infrastructure without sharing library spaces.
2Reliability
If each application is run in a separate virtual machine, then library version conflicts are eliminated, but computing overhead and costs increase
Solution Approach 1:
The patent implements a nested structure where containers are embedded within the server infrastructure without requiring full virtual machine isolation. Each container is a lightweight, user-space virtualization unit that nests within the host operating system, providing application isolation similar to virtual machines but with significantly reduced overhead by sharing the kernel and system resources.
3Adaptability or versatility
If Kubernetes deploys containerized applications without standardized formats, then deployment flexibility is maintained, but parser complexity and support efforts increase
Solution Approach 1:
The patent introduces a universal standardized deployment format that can represent multiple types of containerized applications through a common structure. This single standardized format serves multiple functions by encoding application identity, versioning, and deployment configuration in a unified manner, allowing one parser to handle diverse application types without requiring format-specific processing logic.
Data Source
AI summary
A file is created in a standardized format that defines a type of a containerized application and includes information for deployment of the containerized application. A single parser of the standardized format is thus enabled to deploy different types of containerized applications. The standardized file format includes an application definition. The application definition includes a service, a port list, a container list, a volume mount list, an access mode list, a resource usage list, or any suitable combination thereof. A client device presents a user interface that allows a user to select a containerized application to execute. An application server parses an application template file for the selected containerized application and, based on the information in the application template file, causes one or more servers (e.g., one or more Kubernetes cluster nodes) to execute the containerized application.