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

feat: added helm chart #4065

Closed
wants to merge 7 commits into from
Closed

Conversation

Arvind644
Copy link
Contributor

No description provided.

Copy link
Member

@gabrielmbmb gabrielmbmb left a comment

Choose a reason for hiding this comment

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

Hi @Arvind644, thanks for the PR! Could we make the Elasticsearch deployment optional? I would like to toggle the Elasticsearch deployment based on a value of the Helm template.

@Arvind644
Copy link
Contributor Author

Hi @Arvind644, thanks for the PR! Could we make the Elasticsearch deployment optional? I would like to toggle the Elasticsearch deployment based on a value of the Helm template.

@gabrielmbmb Does I have to make optional deployment for all of these - elasticsearch-deployment.yaml , elasticsearch-pvc.yaml, elasticsearch-service.yaml or only for elasticsearch-deployment.yaml file.

@davidberenstein1957 davidberenstein1957 added the team: ml Indicates that the issue or pull request is owned by the Machine Learning (ML) team label Oct 31, 2023
@Arvind644
Copy link
Contributor Author

@gabrielmbmb I have done all the changes, please review my PR.

@davidberenstein1957 davidberenstein1957 changed the title added helm chart feat: added helm chart Nov 6, 2023
Copy link

@jakemiller649 jakemiller649 left a comment

Choose a reason for hiding this comment

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

I've added a few suggestions from having deployed Argilla recently (I'm not part of Argilla team)

image: argilla/argilla-server:latest
env:
- name: {{ .Values.argilladeployment.name }}
value: "http://elasticsearch:9200"

Choose a reason for hiding this comment

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

This should also be Values.argilladeployment.elasticurl

Copy link
Contributor

Choose a reason for hiding this comment

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

- name: argilla-server
image: argilla/argilla-server:latest
env:
- name: {{ .Values.argilladeployment.name }}

Choose a reason for hiding this comment

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

This env name is required by Argilla and wouln't change between deployments. Leaving it as ARGILLA_ELASTICSEARCH should suffice.

Copy link
Contributor

Choose a reason for hiding this comment

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

{{- end }}
containers:
- name: argilla-server
image: argilla/argilla-server:latest

Choose a reason for hiding this comment

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

Suggestion: swap latest for something like Values.imageTag in case users want to pin the image version (e.g., to 1.16 or something)

Copy link
Contributor

Choose a reason for hiding this comment

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

value: "http://elasticsearch:9200"
ports:
- containerPort: 6900
resources:

Choose a reason for hiding this comment

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

Suggestions: resources often vary among deployments, and so making these into Values values is probably a good practice

Copy link
Contributor

Choose a reason for hiding this comment

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

@@ -0,0 +1,18 @@
apiVersion: autoscaling/v2

Choose a reason for hiding this comment

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

Suggestion: wrap HPAs in something like {{- if .Values.autoscaling.enabled }}

Copy link
Contributor

Choose a reason for hiding this comment

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

@@ -0,0 +1,38 @@
apiVersion: apps/v1

Choose a reason for hiding this comment

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

Suggestion: I would consider adding a PVC for the Argilla deployment so that workspaces/users persist beyond restarts/redeployments and mount it to ARGILLA_HOME_PATH.

@davidberenstein1957
Copy link
Member

davidberenstein1957 commented Nov 13, 2023

Thanks a lot for your help @jakemiller649 and @Arvind644 💪🏽

@davidberenstein1957
Copy link
Member

@Arvind644, are you able to continue work on this or can @gabrielmbmb, further fine-tune the contribution?

@davidberenstein1957
Copy link
Member

As per some suggestions of Robert Pack:

  • Ingress assumes NGINX, and would usually be optional
  • Allow for using Elastic operator to handle elastic deployment
  • Make “build in” elastic configurable – e.g. use VolumeClaim template
  • Improve parameter naming
  • Align HPA config with “conventions” – I.e. enable via flag and have static replicaCount variable if not activated.
  • Allow for injecting some configuration via configmaps / secrets etc …

@bikash119
Copy link
Contributor

As per some suggestions of Robert Pack:

* Ingress assumes NGINX, and would usually be optional

* Allow for using Elastic operator to handle elastic deployment

* Make “build in” elastic configurable – e.g. use VolumeClaim template

* Improve parameter naming

* Align HPA config with “conventions” – I.e. enable via flag and have static replicaCount variable if not activated.

* Allow for injecting some configuration via configmaps / secrets etc …

@bikash119 bikash119 mentioned this pull request Sep 21, 2024
@davidberenstein1957
Copy link
Member

closing because of #5512 . Thanks @bikash119 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team: ml Indicates that the issue or pull request is owned by the Machine Learning (ML) team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants