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

Add datasets-server-worker to the Kube cluster #236

Merged
merged 21 commits into from
May 11, 2022
Merged

Add datasets-server-worker to the Kube cluster #236

merged 21 commits into from
May 11, 2022

Conversation

severo
Copy link
Collaborator

@severo severo commented May 6, 2022

see #223

@severo severo mentioned this pull request May 6, 2022
14 tasks
@severo severo marked this pull request as draft May 6, 2022 14:39
@severo severo changed the base branch from main to kube May 6, 2022 15:58
Base automatically changed from kube to main May 9, 2022 07:30
severo added 6 commits May 9, 2022 08:58
also: fix the dev configuration (typo on the name)
this way, two instances of datasets-server can run on the same
namespace, with different domain names. Fixes
#227 (comment)
* docs: ✏️ clarify doc about Release and Instance name

* fix: 🐛 use the release name to name all the objects

this way, mongo, which prefixes its name with the release, appears in
the same "group" of pods when ordered alphabetically

* fix: 🐛 remove "public," from cache-control

it is not needed (public is only meant to force public caching for
authenticated requests, which is not the case). And it prevented nginx
to correctly cache the responses based on cache-control.

* refactor: 💡 create one template directory per service

Also: use a static name for the containers (see
7abd07d#r73243800)

* feat: 🎸 ignore cpu and ram tests if MAX set to 0

Also: add doc to allow using HF_DATASETS_CACHE and HF_MODULES_CACHE to
set the datasets library cache directories.

* feat: 🎸 add NFS for /assets and dataset library /cache

Also: remove the tests for the load (cpu/ram) in the workers. Note: we
run the containers with user 1000 and group 3000, and use an
initContainer to ensure the mounted volumes from NFS use these user and
group. See #241 for
a possible security improvement on this.
@severo severo marked this pull request as ready for review May 10, 2022 15:52
@severo severo requested a review from XciD May 10, 2022 15:52
@XciD
Copy link
Member

XciD commented May 11, 2022

Very nice job. LGTM

@severo
Copy link
Collaborator Author

severo commented May 11, 2022

Thanks a lot for the review!

@severo severo merged commit f1e8397 into main May 11, 2022
@severo severo deleted the kube-workers branch May 11, 2022 08:55
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.

2 participants