Can this chart be used with a preexisting postgres server?

[totycro]

I've tried to set postgrescluster.enabled to false. db.enabled is false by default, but currently the services fail to start because the DB credentials are missing.

This is not surprising, but is there a way to pass them in with this chart or is it mandatory to use either postgrescluster.enabled or db.enabled?

The documentation here seems to suggest that db.settings.secrets should be used: https://eoapi.dev/deployment/#via-eoapi-k8s

But the values here say that db is deprecated: https://github.com/developmentseed/eoapi-k8s/blob/main/helm-chart/eoapi/values.yaml#L59

[vincentsarago]

there is an open issue about this #133

I'm not quite sure what its status

cc @pantierra @ividito

[pantierra]

To the best of my knowledge, there hasn't been any active development on this recently. However, we can prioritize it moving forward. Also, collaboration is always welcome—feel free to submit any fixes or improvements via pull requests, and we'll ensure they get reviewed promptly.

[ividito]

Postgres credentials and connection details can be provided as environment variables to each service. An example of how these are populated through db.settings is here:

eoapi-k8s/helm-chart/eoapi/templates/db/secrets.yaml

Lines 8 to 17 in e485580

	stringData:
	{{- range $envKey, $envValue := .Values.db.settings.secrets }}
	{{ upper $envKey }}: "{{ $envValue }}"
	{{- /* stac-utils seems to require different environment variable for postgres so handle here via if/else to
	avoid having to pass more arg secrets */ -}}
	{{- if eq $envKey "PGPASSWORD" }}
	POSTGRES_PASS: "{{ $envValue }}"
	{{- end }}
	{{- if eq $envKey "PGDATABASE" }}
	POSTGRES_DBNAME: "{{ $envValue }}"

postgrescluster also provides lots of options to use external DBs, but it generally requires setting up a primary cluster through PGO first AFAIK.

[totycro]

So the credentials and connection details would have to be passed in via envSecrets for each service?

eoapi-k8s/helm-chart/eoapi/templates/services/deployment.yaml

Lines 68 to 72 in e485580

	{{- if index $v "settings" "envSecrets" }}
	{{- range $secret := index $v "settings" "envSecrets" }}
	- secretRef:
	name: {{ $secret }}
	{{- end }}

I guess settings.envVars would work too, although then the credentials would be exposed as helm values and in a config maps.

I think an example of how to do this would be a great addition to the docs.