Autonomous Kubernetes Sub-Operator Generation via Template Registry

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing Kubernetes operator management is complex and time-consuming, especially when managing workloads on non-cloud platforms like IBM z/OSMF, requiring manual creation of operator bundles and docker images, which can be challenging in environments without internet connectivity and leads to inefficiencies like the need for docker-in-docker approaches.

Innovation Solution

The solution involves dynamically generating Kubernetes operator metadata and sub-operators based on templates, using a sub-operator registry server to convert sub-operator bundles into sub-operators, and managing their lifecycle, thereby bypassing the need for manual bundle creation and docker-in-docker processes, allowing for autonomous operator creation and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual creation of operator bundles and docker images is used, then operators can be created for non-cloud platforms, but the process becomes complex and time-consuming

Engineering Contradiction:

Improveability to manage workloads on non-cloud platformsVSAvoidcomplexity of operator creation process

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system enables autonomous operator creation where the operator SDK automatically generates operator bundles and sub-operators from templates without requiring manual intervention. The processing device automatically converts sub-operator bundles into sub-operators and manages their lifecycle, eliminating the need for manual bundle creation and docker image handling.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system uses pre-defined templates that contain the structure and metadata for operator bundles. These templates are prepared in advance, allowing the system to quickly generate operators by filling in specific details rather than creating everything from scratch, significantly reducing the time and complexity of operator creation.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If manual creation of operator bundles and docker images is used, then operators can be created, but the process requires internet connectivity and docker-in-docker approaches

Engineering Contradiction:

Improveability to create operator bundlesVSAvoidease of operator bundle creation

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system performs automatic conversion of sub-operator bundles into sub-operators using a processing device, eliminating the need for manual docker image creation and internet connectivity. The lifecycle management is automated, allowing operators to be created and managed in isolated environments without requiring external resources.

Inventive Principle:

Principle #25Self-service

3Productivity

If traditional docker image handling is used, then operators can be deployed, but performance is limited and scalability is reduced

Engineering Contradiction:

Improveoperator management efficiencyVSAvoidcomplexity of docker image handling

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system extracts the operator bundle conversion process from the traditional docker image handling workflow. By using a processing device to directly convert sub-operator bundles into sub-operators, the system eliminates the intermediate docker image step, reducing complexity and improving performance while maintaining the ability to deploy operators efficiently.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS11693649B2Autonomous Kubernetes operator creation and management

Publication Date: 2023.07.04 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A computer-implemented method includes dynamically generating a sub-operator bundle based on a template. The method further includes converting, by a processing device using a sub-operator registry server, the sub-operator bundle into a sub-operator. The method further includes providing, by the processing device using the sub-operator registry server, the sub-operator to a catalog.