Closed mwallschlaeger closed 7 months ago
Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
Quite a breaking change but you documented it clearly. I would have avoid to bring not related stuff in the PR (like renaming unrelated fields or removing postgres operatore UI) but looking good to me.
Description
CHANGED VALUES.YAML. This may not be compatible with previous versions.
This issue target the situation that you already have a postgres-operator running in your cluster and want to use it without using the external database configuration in geonode-k8s.
So from now on user can choose what kind of postgres type the gonna use by setting the
postgres.type
variable ether tooperator
orexternal
. If your're using the operator you can further decide to install the postgres-operator into your cluster by setting thepostgres-operator.enabled = True
, if not geonode-k8s expects a postgres operator to be available inside your cluster. When settingpostgres.type
toexternal
you need to set your database passwords inside the values.yaml like describe in docs/external_database or provide an self spinned secret set defined in:postgres.external.secret.existingSecretName
.postgres: type: operator operator: storageSize: 2Gi numberOfInstances: 1 postgres_version: 15
postgres-operator: enabled: True
postgres: type: operator operator: storageSize: 2Gi numberOfInstances: 1 postgres_version: 15
postgres: type: external username: postgres geonode_databasename_and_username: geonode geodata_databasename_and_username: geodata
external: hostname: "external-postgres.com" port: 5432 secret: postgres_password: please-fill-out geonode_password: please-fill-out geodata_password: please-fill-out
postgres-operator: enabled: False
postgres: type: external username: postgres geonode_databasename_and_username: geonode geodata_databasename_and_username: geodata
external: hostname: "external-postgres.com" port: 5432 secret: existingSecretName: "geonode-postgres-db-passwords"
postgres-operator: enabled: False