February 21, 2024 - Learn how to deploy Postgres in Kubernetes with ConfigMap. Our PostgreSQL Support team is here to help you with your questions and concerns.

February 17, 2026 - Learn how to create the PostgreSQL instance, ConfigMap, and Deployment objects

October 8, 2020 - apiVersion: v1 kind: ConfigMap metadata: name: pg-hba-configmap data: pg_hba.conf: |+ # TYPE DATABASE USER ADDRESS METHOD # Some personal settings here --- apiVersion: apps/v1 kind: StatefulSet metadata: name: db spec: selector: matchLabels: app: db serviceName: db replicas: 1 template: metadata: labels: app: db spec: nodeSelector: db: 'true' containers: - name: db image: kartoza/postgis:10.0-2.4 volumeMounts: - name: data-volume mountPath: /var/lib/postgresql - name: pg-hba-config-volume mountPath: /var/lib/postgresql/10/main/pg_hba.conf subPath: pg_hba.conf volumes: - name: data-volume hostPath: path: /data/db - name: pg-hba-config-volume configMap: name: pg-hba-configmap

This lab guided you through the process of creating a Kubernetes ConfigMap that securely initializes your PostgreSQL database within a Minikube environment.

January 22, 2024 - This article will serve as a guide for installing PostgreSQL on Kubernetes, covering pre-requisites such as setting up Kubectl, Kubernetes clusters, and Docker. It guides through dockerizing PostgreSQL, configuring persistent storage, deploying ...

July 2, 2021 - So, let’s create a ConfigMap and modify the StatefulSet YAML as shown below. # PostgreSQL StatefulSet ConfigMap apiVersion: v1 kind: ConfigMap metadata: name: postgres-db-config labels: app: postgresql-db data: POSTGRES_DB: testdb POSTGRES_USER: ...

April 27, 2022 - 1. Create a new YAML configuration file (postgres-configmap.yaml) and populate the following configuration. The configuration below creates a ConfigMap named postgres-secret for the postgres application and a database called appdb.

September 8, 2020 - Data stored in a ConfigMap not encrypted. These Kubernetes resources should be only be used with data that is non-sensitive. apiVersion: v1 kind: ConfigMap metadata: name: postgres data: POSTGRES_DB: myapp_production

March 25, 2026 - If the pod is rescheduled, Kubernetes reattaches the same volume so your data remains available. Create a dedicated namespace so database resources stay isolated from application resources. apiVersion: v1 kind: Namespace metadata: name: postgres-demo ... Use a Secret for passwords and a ConfigMap ...

December 15, 2025 - A manual Postgres deployment on Kubernetes allows you to fine-tune a deployment configuration. See the sections below to create a custom Postgres deployment from scratch. Create the ConfigMap resource, which contains deployment process data:

November 28, 2017 - $ kubectl exec -it postgres-3585693371-xnzjv bash root@postgres-3585693371-xnzjv:/# psql -U user -d url_shortener_db psql (9.6.5) Type "help" for help.url_shortener_db=# ConfigMaps can also be defined by a manifest with data in a key/value form, but for the sake of example, we’ll load the content from an external file, config.yaml which contains a single entry (cough!) to set the logger level:

August 29, 2023 - kind: PersistentVolume apiVersion: ... path: "/mnt/data" A ConfigMaps in Kubernetes lets us mount files on containers without the need to make changes to the Dockerfile or rebuilding the container image....

For each namespace where a Kubegres resource is created, Kubegres controller creates a base ConfigMap resource with this contents. That base ConfigMap contains the default configs for all Kubegres resource(s) in that namespace. It defines default contents for "postgres.conf", "pg_hba.conf" and a backup logic in "backup_database.sh".

November 21, 2025 - A ConfigMap is an API object used to store non-confidential data in key-value pairs. Pods can consume ConfigMaps as environment variables, command-line arguments, or as configuration files in a volume.

apiVersion: apps/v1 kind: Deployment metadata: name: reporting-app-deployment labels: app: reporting-app spec: replicas: 2 selector: matchLabels: app: reporting-app template: metadata: labels: app: reporting-app spec: containers: - name: reporting-app image: jtburum/project1:v.0.0.4 ports: - containerPort: 3000 env: - name: POSTGRES_USER valueFrom: secretKeyRef: name: reporting-app-secrets key: postgres-db-username - name: POSTGRES_PASSWORD valueFrom: secretKeyRef: name: reporting-app-secrets key: postgres-db-username - name: POSTGRES_URL valueFrom: configMapKeyRef: name: reporting-app-configmap key: database_url

January 23, 2026 - apiVersion: v1 kind: ConfigMap metadata: name: my-postgresql-configmap labels: app: postgres data: log_truncate_on_rotation: "on" log_rotation_age: "1d" log_filename: "postgresql-%A.log" log_rotation_size: "0" logging_collector: "on" Once Kubernetes updates the volume mount, it applies your changes, and the pods will be restarted based on the parameter Restart field value:

kubernetes_use_configmaps Select ... use endpoints option, and configmaps is required. By default, kubernetes_use_configmaps: false, meaning endpoints will be used. docker_image Spilo Docker image for Postgres instances....

August 13, 2022 - The fields <terminal inline>POSTGRES_DB<terminal inline>, <terminal inline>POSTGRES_USER<terminal inline>, and <terminal inline>POSTGRES_PASSWORD<terminal inline> are your secrets, and you can change the values according to your preference. You can edit these values using text editors like vim or nano. The command below creates a new ConfigMap for our PostgreSQL deployment with a custom configuration.

October 25, 2018 - root@postgres-84968677c9-c4z8q:/# env | grep POSTGRES POSTGRES_DB=test POSTGRES_PASSWORD=test POSTGRES_USER=test root@postgres-84968677c9-c4z8q:/# psql -U test psql: FATAL: role "test" does not exist root@postgres-84968677c9-c4z8q:/# psql -U test -d test psql: FATAL: role "test" does not exist · As you can see - the user weren't created. What you expected to happen: Please take a look at the same flow, but for Config Map (it is working as expected): ... apiVersion: v1 kind: ConfigMap metadata: name: postgres-config data: POSTGRES_DB: test POSTGRES_USER: test POSTGRES_PASSWORD: test

Postgres requires the database, user, and password to be supplied as environment variables. Below we create a config map and secret to store the values of these pieces of configuration. apiVersion: v1 kind: ConfigMap metadata: name: db-pg-cm namespace: db data: POSTGRES_DB: minibuildsdb ...