Automated Operator Deployment in Kubernetes via Package Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Deploying a target software operator in a distributed computing environment, such as a Kubernetes environment, can be a complex and time-consuming process, especially when the operator is not listed in the default operator catalog, requiring users to issue numerous commands to integrate it with the Operator Lifecycle Manager (OLM).

Innovation Solution

An operator configuration module automates the configuration and deployment process by obtaining a package defining the target operator, extracting necessary information, generating an operator group and index image, subscribing the operator to the OLM, and deploying it in the environment, allowing for simplified and expedited integration of the operator into the operator management system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual integration process is used to deploy an operator not listed in the default catalog, then the operator can be deployed, but the process becomes complex and time-consuming

Engineering Contradiction:
ImproveAbility to deploy operators not in default catalogVSAvoidComplexity of deployment process
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs self-service by automatically extracting operator information from the package, generating necessary configuration files, and integrating the operator with OLM without requiring manual user intervention for each step

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-generating configuration files, operator group definitions, and subscription manifests before actual deployment, so that when the operator is deployed, all preparatory work is already in place

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If manual integration process is used to deploy an operator not listed in the default catalog, then the operator can be deployed, but the time required increases significantly

Engineering Contradiction:
ImproveAbility to deploy operators not in default catalogVSAvoidTime required for deployment
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system automates the entire integration workflow, performing self-service by automatically extracting operator information from the package, generating necessary configuration files, and integrating the operator with OLM without requiring manual user intervention for each step

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system maintains continuous useful action by automatically proceeding through each deployment step without interruption - from package extraction to configuration generation to OLM integration - eliminating idle time between manual operations

Inventive Principle:
Principle #20Continuity of useful action

3Ease of operation

If automated deployment is implemented, then deployment complexity is reduced, but automation of configuration and deployment processes is required

Engineering Contradiction:
ImproveSimplicity of deployment processVSAvoidLevel of automation required
Core Design Contradiction:
Ease of operationVSExtent of automation

Solution Approach 1:

The system achieves universality by creating a multi-functional automated deployment framework that can handle package extraction, information parsing, configuration file generation, and OLM integration through a single unified process, making the system adaptable to different operator types

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11900089B2Automatically configuring and deploying a software operator in a distributed computing environment from a package
Publication Date: 2024.02.13 RED HAT LLC
  • US11900089B2 patent drawing
  • US11900089B2 patent drawing
  • US11900089B2 patent drawing

AI summary

A software operator can be automatically configured and deployed in a distributed computing environment from a package. For example, a system can receive a command specifying a package for deploying a target operator. In response to receiving the command, the system can automatically configure and deploy the target operator in a computing cluster. This may involve the system extracting a name for the target operator from the corresponding package and assigning an operator group to the target operator. The system can then subscribe the target operator to an operator management system by indicating the name and a namespace of the operator group to one or more application programming interfaces of the computing cluster. The system can also deploy an instance of the target operator in the namespace on the computing cluster.