EDB Postgres AI Hybrid Manager#
EDB Postgres AI Hybrid Manager (HM) is the control plane of the EDB Postgres AI Platform—a sovereign AI, analytics, and Postgres management solution that runs anywhere you run Kubernetes. It offers a unified experience for deploying databases, running GenAI workloads, and scaling Postgres-native analytics across cloud, on-premises, or hybrid environments.
It is currently supported on the follow Kubernetes distributions for on-premises: Red Hat OpenShift (RHOS), Rancher RKE2, and for in-cloud: Amazon EKS, and Google GKE.
- What you can do
- Hybrid Manager Innovation Release Notes
- Hybrid Manager dual release strategy
- Innovation Release release notes
- Hybrid Manager 1.4.0 release notes
- Contributing Innovation Releases
- Hybrid Manager 2025.11.0 release notes
- Hybrid Manager 2025.12.0 release notes
- Hybrid Manager 2026.1.0 release notes
- Hybrid Manager 2026.2.0 release notes
- Hybrid Manager 2026.3.0 release notes
- Hybrid Manager 2026.4.1 release notes
- Hybrid Manager 2026.5.0 release notes
- Hybrid Manager 2026.5.1 release notes
- Innovation Release release notes
- Hybrid Manager dual release strategy
- EDB Postgres AI Hybrid Manager
- Why Hybrid Manager?
- Key capabilities
- Supported environments
- Integrated solutions
- Learn more
- Get started
- Hybrid Manager architecture
- Supported database types
- Known issues
- Multi-DC
- Core platform and resources
- Cross-stream upgrade issues for OpenShift users
upm-beacon-agentmemory limits are insufficient in complex environments- IdP configuration fails after upgrade to version 2026.2
accm-serverfails to start due to missing Langflow secret- No
kapp-controllersupport in Hybrid Manager app to pull images - Beacon server enters a crashloop when spire is broken
- SPIRE agent fails to start on RKE2 with SELinux enabled
- Image library discovery fails when duplicate operand images share the same tags and SHA
- Database cluster engine
- Failure to create 3-node PGD cluster when
max_connectionsis non-default - AHA witness node resources are over-provisioned
- HA clusters use
verify-cainstead ofverify-fullfor streaming replication certificate authentication - Second node is too slow to join large HA clusters
- EDB Postgres Distributed (PGD) cluster with 2 data groups and 1 witness group not healthy
- AKS deployments limited to one PGD data group with private access per region
- Network access type defaults to
Privatewhen not explicitly selected on RKE - CNPG operator enters an infinite reconcile loop when bootstrap
Jobcreation is interrupted
- Failure to create 3-node PGD cluster when
- Backup and recovery
- Replica cluster creation fails when using volume snapshot recovery across regions
- Volume snapshot restoration is limited to the same region
- WAL archiving is slow due to default parallel configuration
transporter-dbdisaster recovery (DR) process may fail due to WAL gaps- Full cluster recovery fails with
pg_ctl: server does not shut downerror
- Agent Factory and model management
- Failure to deploy
nim-nvidia-nvclipmodel with profile cache - AI Model cluster deployment stalls if object storage path for model profiles is empty
- Model configuration settings reset after Innovation Release upgrade
- Error page appears when editing knowledge base credentials
- Missing aidb_users role on PGD witness node prevents AI functionality
- GenAI Builder structures and tools execution failure
- Pipeline Designer-created knowledge bases not visible to GenAI Builder
- Editing external inference service parameters returns a name change error
- Missing validation message for invalid external model names
- Pipeline creation fails on PGD clusters with AIDB v6.1
- External cloud-hosted OCR models fail to register via the HM console
- Failure to deploy
- Analytics and tiered tables
- HM console and observability
- False positive backup alerts for Advanced High Availability and Distributed High Availability (PGD) clusters
- Event markers overlapping when displaying two different events
- HTTP 431 “Request Header Fields Too Large” error when accessing the Estate page
- Missing notifications for task and cluster lifecycle events
- WAL storage percent metric displays incorrect values on the monitoring page
- GUC settings aren’t applied until after a restart
- Alert threshold updates intermittently fail to take effect
- Asset Library apps require Project Owner or Project Editor role
- Asset Library apps sorted by package name instead of display name
- Metabase fails to deploy when using an EPAS cluster as its database backend
- Asset Library apps pgAdmin4 and Apache Superset fail to deploy on RHOS
- Editing cryptographic keys for Airflow or Superset causes the app to enter a failed state
- Superset deployment fails with
DuplicateTableerror - Asset Library launch app always uses port 443 regardless of custom portal port
- Asset Library app CPU and memory metrics include failed and completed pod states
- Deleting an app or flow gets stuck due to missing service account
- Asset Library apps may get stuck pending on RHOS when storage classes differ
- Clusters and upgrades
- Agent Factory
- Knowledge base data isn’t replicated to non-primary nodes on PGD clusters
- Index analysis actions fail due to missing
hypopgextension - Deleted clusters still appear in AI components
- Missing validation for required MCP tool parameters
- Some EDB Component tools are non-functional due to incompatible API request formatting
- Advanced high Availability and Distributed High Availability (PGD) witness groups appear in database selection lists
- Text search may match on non-visible fields
- Langflow MCP server components not supported in HM Flow Hosting
- EDB Knowledge Base component returns a 403 error when dragged into Langflow
- EDB Knowledge Base component fails to connect when using a global variable for the database user
- Running a test query against an empty knowledge base returns a 500 error
- Flow Hosting deployment fails intermittently with
FlowValidationError - EDB Model Server component causes agent failures when used with the EDB Airman MCP component
upm-ai-model-server-beacoOOMKills due to insufficient memory limits- Updated Langflow flow changes aren’t immediately reflected in HM after republishing
- Migrations
- Supported Postgres distributions
- Installing Hybrid Manager
- Installing Hybrid Manager
- step-by-step guide
- Configuring SOPs
- Syncing images to a local private registry
- Using the in-cluster container registry
- Configuring image discovery
- Prerequisites
- imageDiscovery
- imagesetDiscoveryContainerRegistryURL
- imagesetDiscoveryAllowInsecureRegistry
- image_discovery_credentials_secret_name
- Generic / on-Premises (RKE2/OpenShift)
- Azure Container Registry (ACR)
- AWS Elastic Container Registry (ECR)
- Additional configuration for package installation
- Google Artifact Registry (GAR)
- GitLab Container Registry
- Customizing secrets
- Implementing TLS certificates
- Configuring object storage
- Deploying Hybrid Manager across multiple data centers
- Enabling Key Management Systems (KMS) for TDE
- Optimizing service mesh memory
- API audit logging
- Migrating from bootstrap to operator installation
- Overview
- Understanding the migration challenge
- Prepare the migration with edbctl
- Manual fallback for edbctl less than 1.7.0
- Configuration mapping reference
- Convert using the migration script
- Helm ownership transfer (manual)
- How it works
- Prerequisites
- Step 1: Delete bootstrap deployments
- Step 2: Transfer Helm ownership - ServiceAccount
- Step 3: Transfer Helm ownership - CRDs
- Step 4: Transfer Helm ownership - ClusterRoles
- Step 5: Transfer Helm ownership - ClusterRoleBindings
- Step 6: Transfer Helm ownership - Roles
- Step 7: Transfer Helm ownership - RoleBindings
- Step 8: Transfer Helm ownership - Services
- Step 9: Transfer Helm ownership - Webhook Configurations
- Step 10: Verify ownership transfer
- Support
- Next steps
- Troubleshooting Hybrid Manager installations
- Installing Hybrid Manager
- Using Hybrid Manager
- Where to start
- For users
- For Kubernetes administrators
- Hybrid Manager Terminology
- Hybrid Manager console
- For Users of Hybrid Manager
- Projects
- Working with clusters
- Upgrading database clusters in Hybrid Manager
- Migrating databases with Hybrid Manager
- Asset management
- Backups and restores
- EDB Hybrid Manager Chat Agent
- Governance in Hybrid Manager
- Hybrid Manager CLI - edbctl
- Interacting programmatically with HM
- Managing identity providers
- For Kubernetes Administrators
- Managing users in Hybrid Manager
- Monitoring with Hybrid Manager
- Upgrading Hybrid Manager
- Hybrid Manager backup and disaster recovery (DR)
- Enabling the Migration Portal AI Copilot
- Troubleshooting Hybrid Manager
- Using query recommendations in Hybrid Manager
- Using query recommendations in Hybrid Manager
- Who uses query recommendations?
- What are query recommendations?
- Why use query recommendations?
- When to use query recommendations
- How query recommendations work
- Integrating query recommendations into your tuning process
- Workflow: From query to optimization
- Requirements for external clusters
- Example scenarios
- Supported recommendation types
- Related information
- Agent Factory in Hybrid Manager
- Example AI solutions you can build
- Agent Factory in Hybrid Manager workloads
- How Agent Factory fits within Hybrid Manager
- Sovereign AI in Hybrid Manager
- Get started
- Getting Started with AI Factory
- Understand the AI Factory Architecture
- Model Management
- Model Management on Hybrid Manager
- Deploy Agent Factory with Hybrid Manager UI
- Overview
- Prerequisites
- Step 1: Configure Registry Authentication
- Step 2: Access Model Library
- Step 3: Deploy Model Server Cluster
- Step 4: Monitor Deployment Status
- Step 5: Configure API Access
- Step 6: Build Gen AI Applications
- Step 7: Update and Manage Models
- High availability and isolation for Langflow flows
- Troubleshooting
- Additional Resources
- External inference services
- Build with AI
- Operate & Observe AI Factory
- Analytics in Hybrid Manager
- Sovereign Data and Agent Factory
- Why choose a hardware-based system?
- What’s inside
- Supported workloads
- Hardware configurations
- Explore capabilities