Context-Aware Application Group Re-Registration for Kubernetes Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing application management systems in Kubernetes environments fail to capture ownership, history, and lineage of applications, leading to ineffective data protection and lack of context awareness, especially in multi-admin scenarios, resulting in lost context and authorization challenges during retrieval and recovery.

Innovation Solution

A system and method for context-aware application group management using instance and context IDs to track and re-register application groups, generating re-registration tokens to recreate instances with preserved context, enabling ownership verification and cloning capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If application backups are stored outside the Kubernetes cluster, then data protection is achieved, but ownership information and context are lost

Engineering Contradiction:
Improvedata protectionVSAvoidownership information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent introduces a context database as an intermediary layer between the Kubernetes cluster and external backup storage. This context database stores ownership information, application metadata, and lineage data, acting as a mediator that preserves context while enabling external storage of backup data without losing ownership tracking

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If snapshotting or data backups are performed, then data copies are created for protection, but ownership and lineage information cannot be captured

Engineering Contradiction:
Improvedata protectionVSAvoidlineage information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system performs preliminary actions by capturing and storing application context information, ownership details, and lineage data in the context database before backup operations occur. This ensures that when snapshots or backups are created, the associated metadata and ownership information are already preserved and linked to the backup data

Inventive Principle:
Principle #10Preliminary action

3Reliability

If cloud admin discretion is used for authorization, then security control is maintained, but retrieval efficiency is reduced due to lack of ownership knowledge

Engineering Contradiction:
Improvesecurity controlVSAvoidretrieval efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The context database provides feedback mechanisms that automatically supply ownership information and application context to the authorization system. This enables the system to make informed authorization decisions based on stored ownership data, maintaining security control while improving retrieval efficiency by eliminating the need for manual admin intervention in routine operations

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12411705B2System and method for context-aware application management in container deployment environments
Publication Date: 2025.09.09 DRUVA INC
  • US12411705B2 patent drawing
  • US12411705B2 patent drawing
  • US12411705B2 patent drawing

AI summary

A system for context-aware application group management in a container deployment environment is presented. The system includes a memory storing one or more processor-executable routines and a processor. The processor is configured to execute the one or more processor-executable routines to receive an instance identifier (ID) corresponding to an application group based on a re-registration request for the application group by the user; identify an instance corresponding to the instance ID from an instance database and a context based on the instance from a context database; generate a re-registration token comprising a context ID corresponding to the context, and initiate a re-registration workflow to create a new instance of the application group based on the re-registration token and the context ID. A related method is also presented.