hashmapinc / hashmapinc/Monocker

As a developer, I would like the registry to discover models directly from a shared PV

Open
#31 0 comments 0 reactions 1 assignee Claimed by @randypitcherii View on GitHub
to do
Dominant language
Python
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Description

It's dumb to force each monocker-model instance to register with the registry. It's too tightly coupled and not microservicey.

It's better to use a shared PV to hold models (a pbi exists already to implement this). Then, the registry can do a simple ls on the shared volume to get available models.

This also allows monocker-models to exist behind a load-balancing service in k8s.

In short, this is definitely the way to go.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.