Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Fixes #227] Bug: defining postgres-operator.storageClass is not part of postgres-operator #234

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions charts/geonode/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -153,7 +153,7 @@ Helm Chart for Geonode. Supported versions: Geonode: 4.4.0, Geoserver: 2.24.4-v1
| geoserver.extraPodEnv | string | `""` | Define this for extra GeoServer environment variables Format: extraPodEnv: | - name: KEY_1 value: "VALUE_1" - name: KEY_2 value: "VALUE_2" |
| geoserver.force_reinit | bool | `true` | set force reinit true so that changing passwords etc. in Values.yaml will take effect after restarting the pod this on the other hand will increase pod initializing time, only change if you know what you are doing |
| geoserver.image.name | string | `"geonode/geoserver"` | geoserver image docker image (default in zalf namespace because geonode one was not up to date) |
| geoserver.image.tag | string | `"2.24.4-v1"` | geoserver docker image tag |
| geoserver.image.tag | string | `"2.24.3-latest"` | geoserver docker image tag |
| geoserver.imagePullPolicy | string | `"IfNotPresent"` | geoserver image pull policy |
| geoserver.imagePullSecret | string | `""` | pull secret to use for geoserver image |
| geoserver.port | int | `8080` | geoserver port |
Expand Down Expand Up @@ -193,7 +193,6 @@ Helm Chart for Geonode. Supported versions: Geonode: 4.4.0, Geoserver: 2.24.4-v1
| postgres-operator.enabled | bool | `true` | enable postgres-operator (this or postgresql.enabled NOT both ) |
| postgres-operator.operatorApiUrl | string | `"http://{{ .Release.Name }}-postgres-operator:8080"` | ??? |
| postgres-operator.podServiceAccount | object | `{"name":""}` | not setting the podServiceAccount name will leed to generation of this name. This allows to run multiple postgres-operators in a single kubernetes cluster. just seperating them by namespace. |
| postgres-operator.storageClass | string | `nil` | postgress pv storageclass |
| postgres.external.hostname | string | `"my-external-postgres.com"` | |
| postgres.external.port | int | `5432` | |
| postgres.external.secret.existingSecretName | string | `""` | name of an existing Secret to use. Set, if you want to separately maintain the Secret. |
Expand All @@ -209,6 +208,7 @@ Helm Chart for Geonode. Supported versions: Geonode: 4.4.0, Geoserver: 2.24.4-v1
| postgres.operator.parameters.work_mem | string | `"64Mb"` | |
| postgres.operator.pod_name | string | `"postgresql"` | pod name for postgres containers == teamID for mainifest |
| postgres.operator.postgres_version | int | `15` | postgres version |
| postgres.operator.storageClass | string | `nil` | postgress pv storageclass |
| postgres.operator.storageSize | string | `"3Gi"` | Database storage size |
| postgres.schema | string | `"public"` | database schema |
| postgres.type | string | `"operator"` | type of used postgres: "operator" or "external". \ if external is used, host, port and password have to be set in postgres.external using values or external secret if operator is used, host port and passwords get set automatically using postgres-operator. If your Kubernetes cluster does not have a running postgres-operator, you can install the postgres-operator with postgres-operator.enabled = true |
Expand Down Expand Up @@ -246,4 +246,4 @@ Helm Chart for Geonode. Supported versions: Geonode: 4.4.0, Geoserver: 2.24.4-v1
| rabbitmq.requests.memory | string | `"1Gi"` | requested memory as in resource.requests.memory (https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/) |

----------------------------------------------
Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0)
Autogenerated from chart metadata using [helm-docs v1.13.1](https://github.com/norwoodj/helm-docs/releases/v1.13.1)
1 change: 1 addition & 0 deletions charts/geonode/templates/postgres/postgresql-operator.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ spec:
teamId: {{ .Release.Name | quote }}
volume:
size: {{ .Values.postgres.operator.storageSize }}
storageClass: {{ .Values.postgres.operator.storageClass }}
numberOfInstances: {{ int .Values.postgres.operator.numberOfInstances }}
users:
{{ .Values.postgres.username }}:
Expand Down
4 changes: 2 additions & 2 deletions charts/geonode/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -679,6 +679,8 @@ postgres:
pod_name: postgresql
# -- Database storage size
storageSize: 3Gi
# -- postgress pv storageclass
storageClass:
# -- number of database instances
numberOfInstances: 1
# -- postgres version
Expand Down Expand Up @@ -710,8 +712,6 @@ postgres-operator:
configLoggingRestApi:
# -- REST API listener listens to this port
api_port: 8080
# -- postgress pv storageclass
storageClass:
# -- not setting the podServiceAccount name will leed to generation of this name. This allows to run multiple postgres-operators in a single kubernetes cluster. just seperating them by namespace.
podServiceAccount:
name: ""
Expand Down