-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Metacat is deployable on Kubernetes, using a Helm Chart #1623
Comments
Hey @artntek nice to see your progress on the Postgres sub chart over in that branch. A small thought -- I've been thinking it would be better to not commit files, and particularly binary files, in the For context: https://stackoverflow.com/q/73599035 When the chart gets built with |
Totally! I was in two minds about this, and ended up following the example I found in dataone_indexer (which has a solr binary checked in). I’d feel better leaving it out. What about the lock file - should that be checked in? |
Yeah, sorry about the indexer -- I've been meaning to change that one too. I'm not sure about the lockfile. It's a good question. I think it is probably not needed and will be generated anyways. Putting it in place would lock upgrades to a specific version for anyone who installed the chart, even if the chart label requested is fairly generic. If we have a really specific chart version listed in the dependencies, then the lock is probably not doing anything different. Let's add |
Exclusions for k8s Metacat v3.0.0+
|
closing this ticket - now tracking separately for:
|
Built on top of the work for #1218 (build a docker image for metacat) - the goal is to be able to use helm to install or upgrade metacat on a k8s cluster.
Issues related to this epic:
Enable Passing Secret Credentials to Metacat via Environment Variables #1635Support DataONE Member Node Configuration when running in k8s #1662The text was updated successfully, but these errors were encountered: