Deployment - EDB Hybrid Manager

Service Overview

The Hybrid Manager Deployment package is a structured, outcome-based engagement designed to safely and rapidly deploy the EDB Hybrid Manager onto your Kubernetes infrastructure. This package provides a predictable pathway from initial architecture discovery to a fully validated, unified control plane capable of database orchestration and observability.

The deployment depends on the selected complexity tier:

*Supported Platforms: https://www.enterprisedb.com/docs/edb-postgres-ai/latest/hybrid-manager/install/planning_arch/#supported-platforms  

Scope of Service

To ensure a successful deployment, the EDB consultant will focus on three key pillars:

• Validation of Hybrid Manager prerequisites and customer readiness
• Configuration and Deployment of Hybrid Manager
• Validation of Standard Operating Procedures (SOPs) for the agreed architecture

In addition to standard engagement assumptions and deliverables (below), this package is focused on installation of the EDB Hybrid Manager software solution - we assume that:

• Underlying Kubernetes foundation satisfies EDB minimum requirements (see LINK) as examples, deployment in dedicated cluster, with compliant object storage, image registry and ingress solutions
• EDB pre-sales to validate these requirements in advance of any request for services

Workstreams 

The following workstreams are designed to drive the implementation to completion:

• Environment Readiness Validation: EDB will validate:
  • Required node sizing
  • Prerequisites to be implemented
  • Component to use-case mapping
• Deployment & Integration: EDB will:
  • Perform an environment readiness assessment to validate your underlying Kubernetes cluster, networking, and storage.
  • EDB will then prepare the Hybrid Manager configuration (values.yaml), integrate Identity Providers (IdP) and Key Management Services (KMS), and;
  • Execute the installation of the Hybrid Manager Control Plane.
• Post installation Validation: In order to validate core DBaaS & Observability EDB will:
  • Provision a sample Postgres High Availability cluster
  • Validate failover scenarios 
  • Set up backup/recovery (PITR) schedules
• Project Closure: Formal review of completion status and hand-off

Deliverables

• Architecture Decision Record (ADR): A comprehensive blueprint outlining your topology, locality, and infrastructure prerequisites.
• Deployed Control Plane: One (1) fully installed, accessible, and operational Hybrid Manager Control Plane.
• Validated Configuration Files: The completed and validated Kubernetes values.yaml configuration files for repeatable deployments.

Roles and Responsibilities

EDB Project Manager:  Responsible for initial planning, task alignment, and project closeout.

EDB Solution Architect: Technical Lead, responsible for design documentation, prerequisite validation, HM config and deployment, SOP Validation and documentation.

Customer Team: Responsible for providing the main point of contact for design requirements. Resources and Roles (or similar Technical Stakeholders) where input may be needed for the engagement include:

• Database Administrator
• DevOps or k8s Administrator
• System Architect
• Infrastructure Manager / K8s / Platform Engineer
• Network Administrator
• Security Officer

Assumptions

• A project kickoff will be conducted to review the service scope and confirm the schedule
• This service is delivered remotely unless otherwise agreed
• EDB will deploy the architecture with any EDB-supported version of Postgres. 
• Deployment is for a non-production environment (no live traffic)
• Customer environment is not air-gapped (unless "Air Gapped Repo Setup" is purchased separately)
• Multi Location is defined as a control plane in up to 2 data centers plus a witness node
• Performance testing and application readiness are not in scope
• Customer will provide the names, title, email, phone number, and area of responsibility of those participating. One person will be designated as the main contact, and will be able to provide access to the people most knowledgeable about the topics to be discussed or examined. 
• Customer will make appropriate personnel available to assist EDB in the performance of the services as needed and requested by EDB in a timely manner so as not to disrupt the project schedule. 
• Customer will not provide Personal Data (as defined in applicable law). Customer agrees that it will work with EnterpriseDB to ensure that all such data is not provided.  
• Customer will ensure timely access to all systems through screen sharing and experts including third parties as required. 
• Customer will assign the appropriate resources with the appropriate privileges for the task being planned for any screen sharing sessions as needed throughout the engagement.
• Customer will provide timely feedback on all deliverables. Deliverables without commentary within 5 business days will be deemed as delivered.

Prerequisites

• Customer will provide resource availability for workshop planning and a point of contact for coordination. 
• Server prerequisites will be prepared by the customer team before the kickoff of the project.
• Customer is responsible for providing all necessary internal design and project related documentation and requirements where EDB is required to analyze, operate, or modify customer implemented systems.
• Customer security team has approved all required software packages.
• Customer is strictly responsible for the provisioning, upgrading, and lifecycle management of the underlying Kubernetes cluster(s).
• Customer must supply a functional Kubernetes environment, valid Block Storage (StorageClasses), S3-compatible Object Storage, and a functional Container Network Interface (CNI) before deployment can begin.
• A dedicated management workstation (Bastion host) with network access to the Kubernetes API and necessary CLI tools (kubectl, helm, edbctl) is mandatory for the deployment.