Skip to content

Comments

feat: add shared-resources chart#220

Open
Ivo-Yankov wants to merge 5 commits intomainfrom
postgres-redis
Open

feat: add shared-resources chart#220
Ivo-Yankov wants to merge 5 commits intomainfrom
postgres-redis

Conversation

@Ivo-Yankov
Copy link
Contributor

@Ivo-Yankov Ivo-Yankov commented Feb 2, 2026

Description

This PR adds a new chart used for deploying shared resources - Postgres and Redis.
The current implementation copies and modifies the hedera-mirror chart from the Mirror node.

Signed-off-by: Ivo Yankov <ivo@devlabs.bg>
Signed-off-by: Ivo Yankov <ivo@devlabs.bg>
@Ivo-Yankov Ivo-Yankov changed the title Postgres redis feat: add shared-resources chart Feb 2, 2026
Signed-off-by: Ivo Yankov <ivo@devlabs.bg>
Signed-off-by: Ivo Yankov <ivo@devlabs.bg>
@Ivo-Yankov Ivo-Yankov marked this pull request as ready for review February 5, 2026 11:55
@Ivo-Yankov Ivo-Yankov requested review from a team as code owners February 5, 2026 11:55
jan-milenkov
jan-milenkov previously approved these changes Feb 5, 2026
Signed-off-by: Ivo Yankov <ivo@devlabs.bg>
Comment on lines +32 to +40
- alias: postgresql
condition: postgresql.enabled
name: postgresql-ha
repository: oci://registry-1.docker.io/bitnamicharts
version: 15.3.17
- condition: redis.enabled
name: redis
repository: oci://registry-1.docker.io/bitnamicharts
version: 22.0.7
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say we should open a github issue to move away from bitnami: bitnami/charts#35164

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do any of these values apply to this chart? if not, then it belongs in solo and not in solo-charts/solo-shared-resources

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this appears to be configurations needed for mirror node. I would say anything mirror node related belongs in Solo, not in solo-charts.

It is okay to store the redis information, so that solo can look it up to create the secrets needed for mirror node

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this appears to be configurations needed for mirror node. I would say this belongs in Solo, not in solo-charts.

Comment on lines +73 to +80
{{ if .Values.postgresql.enabled -}}
admin-password: {{ coalesce .Values.postgresql.pgpool.adminPassword (get $passwords "admin-password" | default "" | b64dec) (randAlphaNum 40) | quote }}
PGPOOL_POSTGRES_CUSTOM_PASSWORDS: "{{ $graphqlPassword }},{{ $grpcPassword }},{{ $importerPassword }},{{ $ownerPassword }},{{ $restPassword }},{{ $restJavaPassword }},{{ $rosettaPassword }},{{ $web3Password }}"
PGPOOL_POSTGRES_CUSTOM_USERS: "{{ $graphqlUsername }},{{ $grpcUsername }},{{ $importerUsername }},{{ $ownerUsername }},{{ $restUsername }},{{ $restJavaUsername }},{{ $rosettaUsername }},{{ $web3Username }}"
password: {{ coalesce .Values.postgresql.postgresql.password (get $passwords "password" | default "" | b64dec) (randAlphaNum 40) | quote }}
repmgr-password: {{ coalesce .Values.postgresql.postgresql.repmgrPassword (get $passwords "repmgr-password" | default "" | b64dec) (randAlphaNum 40) | quote }}
POSTGRESQL_TIMEZONE: "UTC"
{{ end -}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this section makes sense to keep, but all of the mirror node settings does not belong here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants