search

ResonantGeoData / RD-OASIS

ResonantGeoData OASIS Deployment
Apache License 2.0
2 stars 1 forks source link

Handle custom containers #42

Open jjnesbitt opened 2 years ago

jjnesbitt commented 2 years ago

Currently, custom containers (one's that are uploaded to django directly) aren't handled, only containers stored on dockerhub are. IMO the way to handle this is to use Amazon ECR to store these custom containers. Then the Kubernetes Job would specify that the image should be pulled from this repo, instead of dockerhub. Here are some kubernetes docs regarding this.

banesullivan commented 2 years ago

I think this is handled, right? Isn't this what we did for the LBNL use case?

jjnesbitt commented 2 years ago

I think this is handled, right? Isn't this what we did for the LBNL use case?

It's handled locally but not if deployed on a K8s cluster.