-
Notifications
You must be signed in to change notification settings - Fork 399
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
Helm chart #5512
Helm chart #5512
Conversation
@davidberenstein1957 : Should we remove the k8s resources files inside examples/deployment/k8s folder once we have helm charts for Elasticsearch and Argilla? We will have hard time keeping the k8s resource yamls and chart templates in sync if we decide to keep them both. Please share your feedback. |
…g external elasticsearch
…d as external service
- Removed k8s resource yamls
- Elasticsearch "built in" is deployed as operator. - Redis, Elasticsearch, Argilla user PV to persist data beyond restarts. - Argilla owner username and password is passed from values.yaml. - 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. If external ES is used, the entries to /etc/hosts are pushed using cm. - Ingress class is made configurable and can be set in values.yaml. - TODO: Add a readme.md for developers to use it. - TODO: Add unit tests to check persistence storage usage.
hi @davidberenstein1957 , @frascuchon. Request you to share your feedback on this work as I continue to work on creating readme for this change. I have been able to resolve all the review comments for the original PR 4065.
|
- Updated CHANGELOG.md to include the PR for helm chart based installation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bikash119 for this amazing PR.
I let some comments/questions. I will try the installation later.
Accept change suggested by @frascuchon Co-authored-by: Paco Aranda <[email protected]>
Accept change suggested by @frascuchon Co-authored-by: Paco Aranda <[email protected]>
Accept change suggested by @frascuchon Co-authored-by: Paco Aranda <[email protected]>
Accept change suggested by @frascuchon Co-authored-by: Paco Aranda <[email protected]>
Accept change suggested by @frascuchon Co-authored-by: Paco Aranda <[email protected]>
Accept change suggested by @frascuchon Co-authored-by: Paco Aranda <[email protected]>
- Added steps to get started in minikube cluster for local development
- Updated README.md to include few missing steps
@bikash119 additionally to the addition of Redis as dependency we need a change to run the Argilla server workers to process the background jobs enqueues into Redis. You can take a look to https://github.com/argilla-io/argilla/blob/develop/examples/deployments/docker/docker-compose.yaml#L36-L47 to check how we are running the workers in the Argilla Docker compose example, but the idea is that the instance running the workers should have access to the same config that the server is using and then execute the following: python -m argilla_server worker Thanks for the PR btw ❤️ |
- added a resource yaml for argilla-worker - fixed the ports used for readiness and liveliness probes
- Added labels and selector-labels for worker
…d run integration tests
…e successfully before running integration test
@jfcalvo Thank you for the pointer. I have included it as a different resource to the helm chart. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution @bikash119!!!
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #5512 +/- ##
===========================================
- Coverage 91.23% 91.21% -0.02%
===========================================
Files 145 145
Lines 5964 5964
===========================================
- Hits 5441 5440 -1
- Misses 523 524 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Description
helm lint
to find and fix linting errors in chart templates.Closes #<issue_number>
Type of change
How Has This Been Tested
on dev machine
helm install argilla-dev examples/deployment/k8s/argilla-cart
This should install and start elasticsearch and argilla-server to the k8s cluster
kubectl port-forward service/argilla-dev-argilla-chart 6900:6900
.Checklist