Cloud Native Postgres (CNPG) Deployment

Service Overview

The EDB CNPG Deployment Jump Start helps customers harness the power of Postgres in Kubernetes environments. This engagement focuses on deploying EDB Cloud Native Postgres with best practices for high availability and monitoring, leveraging EDB's expertise to accelerate Kubernetes adoption.

The engagement includes deployment of EDB-supported k8s Operators based on the following complexity tiers:

Scope of Service

Our Consultant will validate the prerequisites, configure and deploy the EDB-supported k8s operator, and validate Standard Operating Procedures (SOPs) for the agreed architecture:

• Onboard: Engagement preparation, review of prerequisites, and scope alignment
• Configuration: Configuration of EDB-supported k8s operator for deployment
• Deployment: Deployment of the Postgres cluster utilizing the EDB-supported k8s Operator , including HA configuration, backups, and monitoring (if applicable)
• Validation: Quality checks, demonstration of the architecture, and review of Standard 
• Operating Procedures (SOPs)
• Project Closure: Formal review of completion status and hand-off

Deliverables

• One (1) installed and operational EDB Postgres cluster on the supported k8s platform
• EDB k8s operator config (yaml) files

Roles and Responsibilities

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

EDB Senior Consultant: Technical Lead, responsible for prerequisite validation, operator 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 k8s operator:https://www.enterprisedb.com/docs/edb-postgres-ai/platforms-and-tools/kubernetes/
• EDB will deploy to any EDB-supported k8s environment:
  EDB Postgres® AI for CloudNativePG™ Cluster
  EDB Postgres® AI for CloudNativePG™ Global Cluster (PGD4k8s)
  CloudNativePG™
• Deployment is for a non-production environment (no live traffic)
• Customer environment allows access to required container registries (unless Air Gap Repo Setup is added).
• 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.
• Security integration (LDAP/AD) is not included.
• Customer is responsible for establishing cross-cluster network connectivity and DNS resolution required for multi-region deployments.

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 preparation and setup of the k8s environment.
• 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 will provide the EDB Consultant or the designated internal resource with cluster-admin privileges (or equivalent RBAC permissions) within the target namespace(s) to deploy the Operator and custom resources.
• Customer must provide a validated K8s Storage Class that meets the IOPS requirements for a production-grade database (e.g., SSD, Premium SSD, or NVMe), and volume based snapshots.
• Customer must provide access to S3 compatible object storage

Standard Operating Procedures

EDB will validate the below test cases as part of the validation process: