Containerized Cloud-Native Cluster Storage Targets for Kubernetes Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy virtual machine and hypervisor approaches face challenges in migrating to container-based systems, particularly in providing cloud-native storage and self-service tools with centralized data management in Kubernetes environments, leading to technological limitations in the rapidly evolving hybrid and multi-cloud landscape.
Innovation Solution
Deploying a cluster node controller as a cloud-native executable container that functions as a storage target, utilizing a storage target interface, and incorporating necessary dependencies into the container's code base to operate independently of host OS and custom code, enabling seamless integration with cloud-provided infrastructure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If legacy virtual machine and hypervisor approaches are used, then centralized data management is achieved, but adaptability to cloud-native Kubernetes environments deteriorates
Solution Approach 1:
The patent creates a containerized copy of the virtualization controller that replicates the storage target interface functionality within the Kubernetes environment. This containerized controller copies the essential data management capabilities while being adapted to run natively in containers, eliminating the need for complex migration from the virtual machine regime.
Solution Approach 2:
The patent changes the deployment parameter from virtual machine/hypervisor architecture to containerized architecture. By transforming the controller into a containerized executable with all dependencies bundled, the system adapts to Kubernetes environments while maintaining centralized data management capabilities through modified deployment parameters rather than architectural overhaul.
2Ease of operation
If containerized executable is deployed with all dependencies, then ease of operation in Kubernetes environments is improved, but device complexity increases
Solution Approach 1:
The patent merges the virtualization controller executable with all its required dependencies into a single containerized unit. This combining of the application and its dependencies simplifies deployment operations in Kubernetes, as the entire storage target interface can be deployed as one self-contained container without complex configuration or separate dependency management.
Solution Approach 2:
The containerized controller is designed with universal functionality to operate in Kubernetes environments while maintaining the centralized data management capabilities of the legacy system. The single containerized executable performs multiple functions including storage management, data orchestration, and interface handling, reducing operational complexity despite increased internal sophistication.
3Adaptability or versatility
If self-contained containerized controller is used, then adaptability to different cloud infrastructure is improved, but loss of information about host OS dependencies increases
Solution Approach 1:
The patent copies all necessary host OS dependencies and custom code into the containerized controller image. This creates a self-contained unit that replicates the required runtime environment within the container, allowing the controller to operate independently of the host OS while retaining all necessary functional dependencies through copied binaries and libraries.
Solution Approach 2:
The patent implements a nested structure where the containerized controller contains within it the necessary dependencies that would normally reside on the host system. The host OS dependencies are nested inside the container image, creating a portable, self-contained unit that maintains all required information about its operational environment without requiring external host OS components.
Data Source
AI summary
Methods, systems, and computer program products. For implementing a container-attached storage facility. A cloud-resident containerized control module is situated in a Kubernetes Pod. A plurality of storage devices are organized into a common access space and made accessible by the cloud-resident containerized control module. In operation, and responsive to receiving a storage I/O request referencing a portion of storage that is addressable via the common access space, the cloud-resident containerized control module redirects the storage I/O request to a storage device of the common access space. Some instances of storage I/Os are redirected toward a cloud-provided block storage facility. Some instances of storage I/Os are redirected to storage devices situated in an on-premises environment.