based on dpage/pgadmin4
pgAdmin4 is the leading Open Source management tool for Postgres, the world’s most advanced Open Source database. pgAdmin4 is designed to meet the needs of both novice and experienced Postgres users alike, providing a powerful graphical interface that simplifies the creation, maintenance and use of database objects.
$ helm repo add runix https://helm.runix.net/
$ helm install runix/pgadmin4
This chart bootstraps a pgAdmin4 deployment on a Kubernetes cluster using the Helm package manager.
To install the chart with the release name my-release
:
$ helm install --name my-release runix/pgadmin4
The command deploys pgAdmin4 on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured durign installation.
Tip: List all releases using
helm list
To uninstall/delete the my-release
deployment:
helm delete --purge my-release
The command removes nearly all the Kubernetes components associated with the chart and deletes the release.
Parameter | Description | Default |
---|---|---|
replicaCount |
Number of pgadmin4 replicas | 1 |
image.repository |
Docker image | dpage/pgadmin4 |
image.tag |
Docker image tag | 4.20 |
image.pullPolicy |
Docker image pull policy | IfNotPresent |
service.type |
Service type (ClusterIP, NodePort or LoadBalancer) | ClusterIP |
service.port |
Service port | 80 |
service.portName |
Name of the port on the service | http |
service.targetPort |
Internal service port | http |
service.nodePort |
Kubernetes service nodePort | `` |
strategy |
Specifies the strategy used to replace old Pods by new ones | {} |
serverDefinitions.enabled |
Enables Server Definitions | false |
serverDefinitions.servers |
Pre-configured server parameters | `` |
ingress.enabled |
Enables Ingress | false |
ingress.annotations |
Ingress annotations | {} |
ingress.hosts.host |
Ingress accepted hostname | nil |
ingress.hosts.paths |
Ingress paths list | [] |
ingress.tls |
Ingress TLS configuration | [] |
extraConfigmapMounts |
Additional configMap volume mounts for pgadmin4 pod | [] |
extraSecretMounts |
Additional secret volume mounts for pgadmin4 pod | [] |
extraContainers |
Sidecar containers to add to the pgadmin4 pod | {} |
extraInitContainers |
Sidecar init containers to add to the pgadmin4 pod | {} |
env.email |
pgAdmin4 default email | [email protected] |
env.password |
pgAdmin4 default password | SuperSecret |
env.pgpassfile |
Path to pgpasssfile (optional) | `` |
persistentVolume.enabled |
If true, pgAdmin4 will create a Persistent Volume Claim | true |
persistentVolume.accessMode |
Persistent Volume access Mode | ReadWriteOnce |
persistentVolume.size |
Persistent Volume size | 10Gi |
persistentVolume.storageClass |
Persistent Volume Storage Class | unset |
securityContext |
Custom security context for pgAdmin4 containers | `` |
resources |
CPU/memory resource requests/limits | {} |
livenessProbe |
liveness probe initial delay and timeout | `` |
readinessProbe |
readiness probe initial delay and timeout | `` |
nodeSelector |
Node labels for pod assignment | {} |
tolerations |
Node tolerations for pod assignment | [] |
affinity |
Node affinity for pod assignment | {} |
podAnnotations |
Annotations for pod | {} |
existingSecret |
The name of an existing secret containing the pgadmin4 default password. | "" |
env.enhanced_cookie_protection |
Allows pgAdmin4 to create session cookies based on IP address | "False" |
Specify each parameter using the --set key=value[,key=value]
argument to helm install
. For example:
$ helm install runix/pgadmin4 --name my-release \
--set env.password=SuperSecret
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example:
$ helm install runix/pgadmin4 --name my-release -f values.yaml
Tip: You can use the default values.yaml