Postgresql database created if changed environment variable in a kubernetes replicaset - postgresql

Question

I created a cluster of kubernetes on local using minikube and I changed the environment variables of the database name to another value than postgresql. I see that everytime I delete a pod and it replicate, creates the default database 'postgres' and the other one that I configured on the environment variables. Is that normal or I do something wrong? I only want to create the single database, the name that I define in the environment variable.
Configuration file:
kind: ReplicaSet
apiVersion: apps/v1
metadata:
name: postgresql-kubernetes-1-7f6b9f97cf
namespace: default
uid: a50e813d-4110-47fc-9708-69e6990d0355
resourceVersion: '1818'
generation: 1
creationTimestamp: '2022-11-19T16:34:04Z'
labels:
k8s-app: postgresql-kubernetes-1
pod-template-hash: 7f6b9f97cf
annotations:
deployment.kubernetes.io/desired-replicas: '1'
deployment.kubernetes.io/max-replicas: '2'
deployment.kubernetes.io/revision: '1'
ownerReferences:
- apiVersion: apps/v1
kind: Deployment
name: postgresql-kubernetes-1
uid: bcc1d5e9-82b3-4edb-9b7b-a67baa7c1117
controller: true
blockOwnerDeletion: true
managedFields:
- manager: kube-controller-manager
operation: Update
apiVersion: apps/v1
time: '2022-11-19T16:34:04Z'
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.: {}
f:deployment.kubernetes.io/desired-replicas: {}
f:deployment.kubernetes.io/max-replicas: {}
f:deployment.kubernetes.io/revision: {}
f:labels:
.: {}
f:k8s-app: {}
f:pod-template-hash: {}
f:ownerReferences:
.: {}
k:{"uid":"bcc1d5e9-82b3-4edb-9b7b-a67baa7c1117"}: {}
f:spec:
f:replicas: {}
f:selector: {}
f:template:
f:metadata:
f:labels:
.: {}
f:k8s-app: {}
f:pod-template-hash: {}
f:name: {}
f:spec:
f:containers:
k:{"name":"postgresql-kubernetes-1"}:
.: {}
f:env:
.: {}
k:{"name":"POSTGRES_DB"}:
.: {}
f:name: {}
f:value: {}
k:{"name":"POSTGRES_PASSWORD"}:
.: {}
f:name: {}
f:value: {}
k:{"name":"POSTGRES_USER"}:
.: {}
f:name: {}
f:value: {}
f:image: {}
f:imagePullPolicy: {}
f:name: {}
f:resources: {}
f:securityContext:
.: {}
f:privileged: {}
f:terminationMessagePath: {}
f:terminationMessagePolicy: {}
f:dnsPolicy: {}
f:restartPolicy: {}
f:schedulerName: {}
f:securityContext: {}
f:terminationGracePeriodSeconds: {}
- manager: kube-controller-manager
operation: Update
apiVersion: apps/v1
time: '2022-11-19T17:02:24Z'
fieldsType: FieldsV1
fieldsV1:
f:status:
f:availableReplicas: {}
f:fullyLabeledReplicas: {}
f:observedGeneration: {}
f:readyReplicas: {}
f:replicas: {}
subresource: status
spec:
replicas: 1
selector:
matchLabels:
k8s-app: postgresql-kubernetes-1
pod-template-hash: 7f6b9f97cf
template:
metadata:
name: postgresql-kubernetes-1
creationTimestamp: null
labels:
k8s-app: postgresql-kubernetes-1
pod-template-hash: 7f6b9f97cf
spec:
containers:
- name: postgresql-kubernetes-1
image: postgres
env:
- name: POSTGRES_DB
value: postgresql_kubernetes_1
- name: POSTGRES_USER
value: superuseryeababy
- name: POSTGRES_PASSWORD
value: superpasswordyeababy
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
imagePullPolicy: Always
securityContext:
privileged: false
restartPolicy: Always
terminationGracePeriodSeconds: 30
dnsPolicy: ClusterFirst
securityContext: {}
schedulerName: default-scheduler
status:
replicas: 1
fullyLabeledReplicas: 1
readyReplicas: 1
availableReplicas: 1
observedGeneration: 1
answer for my question and help me understand how actually a pod works