Skip to content

Epic: Agent Lifecycle Governance #3208

@rrbanda

Description

@rrbanda

Overview

Comprehensive overhaul of agent creation, lifecycle management, and registry in the augment plugin. Ensures all agents follow a governed lifecycle pipeline (draft → review → staging → production → retired) regardless of creation method.

Research Findings

See agent-lifecycle-research.md for full details including:

  • Complete Kagenti API surface map (35+ endpoints)
  • Live cluster exploration results
  • As-is vs to-be user journey maps
  • 7 identified bugs with priority rankings

PRs

P0 (Critical)

P1 (Important)

P2 (Nice-to-have)

  • PR 8 - Update docsContent.ts from 3-stage to 5-stage lifecycle model
  • PR 9 - Research RHDH orchestrator workflows for approval automation
  • PR 10 - Remove or wire orphan AgentCreationWizard component

Key Findings from Cluster Exploration

  1. Kagenti API has DELETE endpoint (DELETE /api/v1/agents/{ns}/{name}) - was not wired to chatAgents cleanup
  2. Two types of agents: API-managed (via backend) and K8s-native (via Helm/kubectl) - only API-managed show in backend list
  3. Auth: Keycloak OIDC with 60s token TTL, both public and confidential clients
  4. RHDH Orchestrator (SonataFlow) is deployed on cluster - potential for approval workflow automation

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions