Self-Service Kubernetes Workload Governance Through Resource Observation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity and scope of containerized applications managed by administrators have exploded, making manual management impractical, especially in terms of policy synthesis, enforcement, and governance, which is exacerbated by infrastructure and application changes, necessitating a reduction in administrative burden.

Innovation Solution

Techniques for automatically generating executable modules that observe and govern infrastructure resources in self-service Kubernetes workloads, reducing memory and CPU demands, and ensuring compliance with policy limitations and governance rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If administrators manually manage containerized applications, then they can maintain policy compliance and governance, but the administrative burden becomes untenable due to explosion of scope and complexity

Engineering Contradiction:
Improvepolicy complianceVSAvoidadministrative burden
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system implements self-service automation where the containerized application autonomously manages its own infrastructure resources. The application automatically observes resource usage, synthesizes policies, generates executable modules, and enforces governance rules without requiring manual administrative intervention. This self-service mechanism resolves the contradiction by maintaining policy compliance through automated self-governance while eliminating the untenable administrative burden of manual management.

Inventive Principle:
Principle #25Self-service

2Reliability

If administrators manually enforce policies and governance rules, then compliance is maintained, but the complexity of ongoing management becomes impractical

Engineering Contradiction:
Improvegovernance complianceVSAvoidmanagement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system replaces the mechanical manual process of policy enforcement with an automated computational system. The containerized application automatically synthesizes policies from governance rules, generates executable modules through code synthesis, and enforces these policies programmatically. This substitution of manual mechanical administration with automated computational mechanisms maintains governance compliance while dramatically reducing management complexity to practical levels.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If self-service Kubernetes workloads are deployed, then agility and flexibility improve, but infrastructure resource governance becomes more difficult

Engineering Contradiction:
Improvedeployment flexibilityVSAvoidresource governance
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements continuous feedback loops where the containerized application autonomously observes its own infrastructure resource usage, compares actual usage against synthesized policies derived from governance rules, and automatically adjusts its behavior to maintain compliance. This self-monitoring and self-correcting feedback mechanism enables self-service Kubernetes workloads to maintain deployment flexibility while automatically managing infrastructure resource governance, making it neither more nor less complex than traditional managed approaches.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250291621A1Observing and governing ongoing use of infrastructure resources when running self-service kubernetes workloads
Publication Date: 2025.09.18 NUTANIX INC
  • US20250291621A1 patent drawing
  • US20250291621A1 patent drawing
  • US20250291621A1 patent drawing

AI summary

Techniques for maintaining a Kubernetes cluster on a computing infrastructure that supports a given data management application. After deploying a Kubernetes cluster-based configuration of a desired state of the data management application, gathering observations of one or more changes pertaining to influencing and/or maintaining the desired state of that data management application, wherein the one or more changes comprise any one or more of, a change to a policy, a new command to the data management application, a change to the data management application itself, or a change to one or more governance rules or regulations. In response to analysis of the one or more changes pertaining to the desired state of the data management application, synthesizing a new desired state so as to determine a set of changes to be made to either the Kubernetes cluster, or to the data management application, or to the computing infrastructure.