* [stable/pgadmin] upgrade to 4.17 and more 4.17: with 4.16 and up `USER: pgadmin` got added to the Dockerfile, this caused an ACL issue. securityContext and initContainers is added to resolve this issue. other: - fixed dynamic PV provisioning - livenessProbe - readinessProbe - added more comments in values.yaml - updated README.md with new configuration items - chart bump version Signed-off-by: Rowan Ruseler <rowanruseler@gmail.com> * [stable/pgadmin] adjusted storageclass name made a mistake with naming the variable different then what is shown in the values.yml example Signed-off-by: Rowan Ruseler <rowanruseler@gmail.com> * [stable/pgadmin] resolved sessions bug by letting the probes go to the correct path Signed-off-by: Rowan Ruseler <rowanruseler@gmail.com>
based on dpage/pgadmin4
pgAdmin
pgAdmin is the leading Open Source management tool for Postgres, the world’s most advanced Open Source database. pgAdmin 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.
TL;DR;
$ helm install stable/pgadmin
Introduction
This chart bootstraps a pgAdmin deployment on a Kubernetes cluster using the Helm package manager.
Install the Chart
To install the chart with the release name my-release:
$ helm install --name my-release stable/pgadmin
The command deploys pgAdmin 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
Uninstall the Chart
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.
Configuration
| Parameter | Description | Default |
|---|---|---|
replicaCount |
Number of pgadmin replicas | 1 |
image.repository |
Docker image | dpage/pgadmin4 |
image.tag |
Docker image tag | 4.17 |
image.pullPolicy |
Docker image pull policy | IfNotPresent |
service.type |
Service type (ClusterIP, NodePort or LoadBalancer) | ClusterIP |
service.port |
Service port | 80 |
ingress.enabled |
Enables Ingress | false |
ingress.annotations |
Ingress annotations | {} |
ingress.hosts |
Ingress accepted hostnames | nil |
ingress.tls |
Ingress TLS configuration | [] |
ingress.path |
Ingress path mapping | `` |
env.username |
pgAdmin default email | chart@example.local |
env.password |
pgAdmin default password | SuperSecret |
persistentVolume.enabled |
If true, pgAdmin 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 pgAdmin 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 | {} |
Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,
$ helm install stable/pgadmin --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 stable/pgadmin --name my-release -f values.yaml
Tip
: You can use the default values.yaml