Agentless GitOps Orchestration Through Centralized Read-Only Access

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional systems for cloud-based infrastructure orchestration using GitOps require agents on clusters, consuming resources and posing security risks, and lack efficient means for infrastructure and cluster orchestration.

Innovation Solution

Implementing a service management and orchestration (SMO) platform with READ ONLY access to a git repository, enabling agentless GitOps for infrastructure, cluster, and application orchestration, preserving resources and enhancing security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If traditional GitOps systems use agents on clusters to perform service orchestration, then service orchestration capability is improved, but computational resources are consumed and security risks increase

Engineering Contradiction:

Improveservice orchestration capabilityVSAvoidcomputational resource consumption

Core Design Contradiction:

Extent of automationVSUse of energy by moving object

Solution Approach 1:

The patent extracts the GitOps agent from the cluster environment and relocates it to a centralized service orchestration platform. This removal eliminates the need for agents running on each cluster, thereby freeing computational resources on clusters while maintaining centralized orchestration capability through the platform that polls the git repository directly.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The service orchestration platform acts as an intermediary between the git repository and the clusters. Instead of agents on clusters directly interacting with git, the centralized platform mediates this interaction by polling the repository and distributing configuration changes to clusters, eliminating the need for local agents while preserving orchestration functionality.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Extent of automation

If traditional GitOps systems use agents on clusters, then service orchestration is enabled, but security risks increase due to read and write access requirements

Engineering Contradiction:

Improveservice orchestration capabilityVSAvoidsecurity risks

Core Design Contradiction:

Extent of automationVSObject-affected harmful factors

Solution Approach 1:

The patent removes the GitOps agent from the cluster environment and consolidates git access functionality into a centralized service orchestration platform. This extraction eliminates security risks associated with agents having read/write access to git repositories on distributed clusters, as only the centralized platform maintains secure credentials and access tokens.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The service orchestration platform serves as a secure intermediary that manages all git repository interactions. By centralizing access control and using secure authentication mechanisms at the platform level, the system eliminates the security vulnerabilities of distributed agents while maintaining necessary read/write access to configuration repositories.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If agents are deployed on clusters for GitOps, then infrastructure orchestration can be performed, but device complexity increases

Engineering Contradiction:

Improveinfrastructure orchestration capabilityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the GitOps agent functionality with the service orchestration platform into a single centralized system. This consolidation eliminates the need for separate agent components on each cluster, reducing system complexity while maintaining comprehensive infrastructure orchestration capabilities through the unified platform.

Inventive Principle:

Principle #5Merging (Combining)

4Ease of operation

If traditional systems use agents for service orchestration, then configuration management is improved, but resource availability for applications decreases

Engineering Contradiction:

Improveconfiguration management capabilityVSAvoidavailable computational resources

Core Design Contradiction:

Ease of operationVSQuantity of substance

Solution Approach 1:

The patent extracts the configuration management agent from the cluster and relocates it to a centralized service orchestration platform. This removal frees computational resources on clusters for application workloads while the centralized platform maintains configuration management capabilities by polling git repositories and distributing updates to clusters without requiring local agents.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS12445427B2Agentless GitOps and custom resources for application orchestration and management

Publication Date: 2025.10.14 RAKUTEN SYMPHONY INC

AI summary

Systems and methods for agentless GitOps and custom resources for application orchestration and management. A system includes a bare metal server running a cloud native application and a plurality of clusters running on the bare metal server, wherein at least a portion of the plurality of clusters executes an application. The system includes a data center automation platform responsible for service management and orchestration for the bare metal server, wherein the data center automation platform subscribes to a git repository to receive updates pertaining to the application, and wherein a read only token is established between the git repository and the data center automation platform.