Skip to content

Conversation

@redmikhail
Copy link
Contributor

Changes to helm charts to add Elastic as one of the supported vector dbs. Also includes fixes to grafana dashboards to eliminate duplication for some of the tiles

- name: PGVECTOR_COLLECTION_NAME
value: {{ .Values.global.db.index }}
{{- end }}
{{- if eq .Values.global.db.type "ELASTIC" }}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we externalize all the variables like the username, url index in values.yaml files, so that it can be overridable

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have parameterized index name . I would prefer to keep url, username "opinionated" for the elastic. Elastic is default user in Elastic cluster, it allows us to benefit from automatically generated secret with credentials instead of creating additional entries to the vault. Alternative user name would require creating this user and explicitly creating RBAC , unnecessary complicating configuration for our demonstration purposes.

value: 'postgresql+psycopg://$(DB_USERNAME):$(DB_PASS)@$(DB_HOST):$(DB_PORT)/$(DB_NAME)'
- name: PGVECTOR_COLLECTION_NAME
value: {{ .Values.global.db.index }}
{{- end }}
Copy link
Collaborator

Choose a reason for hiding this comment

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

same here . can we allow the user to override these values from values.yaml

@day0hero
Copy link
Contributor

day0hero commented May 5, 2025

/lgtm

@sauagarwa sauagarwa merged commit 8cfc0a4 into validatedpatterns:main May 6, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants