Skip to main content
PostgreSQL configuration depends on the selected mapping. RDS or Aurora PostgreSQL can map to generated CloudNativePG resources on Kubernetes or a generated Cloud SQL instance on Google Cloud where that option is offered. The application database and credential resources depend on what the origin declares. Arrows show deployment generation.PostgreSQL configuration depends on the selected mapping. RDS or Aurora PostgreSQL can map to generated CloudNativePG resources on Kubernetes or a generated Cloud SQL instance on Google Cloud where that option is offered. The application database and credential resources depend on what the origin declares. Arrows show deployment generation.PostgreSQL configuration depends on the selected mapping. RDS or Aurora PostgreSQL can map to generated CloudNativePG resources on Kubernetes or a generated Cloud SQL instance on Google Cloud where that option is offered. The application database and credential resources depend on what the origin declares. Arrows show deployment generation.PostgreSQL configuration depends on the selected mapping. RDS or Aurora PostgreSQL can map to generated CloudNativePG resources on Kubernetes or a generated Cloud SQL instance on Google Cloud where that option is offered. The application database and credential resources depend on what the origin declares. Arrows show deployment generation.
The CloudNativePG mapping generates a cluster and, when an application database is declared, a credential Secret. The Cloud SQL mapping generates a managed instance and the application database when declared. Plan data migration separately. Your application’s form factor defines the service options an install can use. Your customer selects an offered option and supplies its customer-owned configuration. The selected integration determines whether the install connects to an existing service or generates new resources in the customer’s environment.

​
How this is different from service equivalents

Service adapters describe how an origin service is realized on a selected target. For example, an offered RDS PostgreSQL mapping can generate Cloud SQL resources on Google Cloud. Customer configuration supplies the fields defined by the selected service schema, within the choices allowed by the form factor. Use its guide to agree on configuration, deployment behavior and operational ownership for an install.

​
Services customers can provide today

PostgreSQL’s guide describes its cloud-managed and appliance-managed deployments, the generated resources and their responsibilities. Use the linked guide for each service’s configuration and deployment scope. If your customer’s required integration is not described, contact us.

​
What your customer configures

Setup collects the fields defined for the selected service. Depending on the integration, those can include service choices, namespaces, capacity settings or connection details. Vendor-owned tuning and customer-owned fields are checked separately when the install profile is built. When setup requests a secret reference, supply the secret through the designated store. Typed secret-reference fields keep the secret’s identifier in the service profile. The consuming integration determines how the reference is resolved and used. Consult that integration’s authentication procedure for database login and rotation. See service configuration and customer secrets for the setup responsibilities, then use the selected service’s guide for its exact fields and behavior.