Chart Files for PostgreSQL Deployment

2nd chunk of `content/en/blog/_posts/2016-09-00-Creating-Postgresql-Cluster-Using-Helm.md`

350b22512b9ffa3cfb89d3723749b4228df8c89578e84b2e00000001000003ef

![HelmBlogDiagram.jpg](https://lh5.googleusercontent.com/Ff3vRGv3RHsrbAvJUFpVTehohw-OI2AeFmeVSVrdJuU0mjx3lKTa07YlaB_a7rW65rfAdupyeSqOT2DyxnSJ6_y4sXY5DhW14qM-vkxRo32969VZEpUNrZ3hIFdwJ9T04Ev6w2to)



This example creates a simple Postgres streaming replication deployment with a master (read-write), and a single asynchronous replica (read-only). You can scale up the number of replicas dynamically.



**Contents**



The example is made up of various Chart files as follows:


|  |  |
| :------------: | :------------: |
|values.yaml |This file contains values which you can reference within the database templates allowing you to specify in one place values like database passwords|
|templates/master-pod.yaml|The postgres master database pod definition.  This file causes a single postgres master pod to be created.
|templates/master-service.yaml|The postgres master database has a service created to act as a proxy.  This file causes a single service to be created to proxy calls to the master database.

Title: Chart Files for PostgreSQL Deployment

Summary

This section describes the chart files used for deploying the PostgreSQL cluster. It includes `values.yaml` which contains configurable values such as database passwords, `templates/master-pod.yaml` which defines the Postgres master database pod, and `templates/master-service.yaml` which creates a service to proxy calls to the master database.