You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create Ingress (may solve some of the log/test issues)
don't run webapp as root
using secrets for passwords
defining site properties overwriting behavior for new vs. existing helm deployments
if path to metacat-site.properties has been changed from the default, provide a helm-friendly way to avoid having to set it again via admin interface.
Persistent Volume mounted at /var/metacat - working, but not poss to reconnect to same PV if Claim deleted when deployment deleted - so now creating claim only once, outside of deployment. Need to review with @mbjones Solved - changed to statefulset
The text was updated successfully, but these errors were encountered:
See Epic #1623
TODO: For MVP Release, in Priority Order
DONE
Dev cluster: run tests against metacat+indexer setupDev cluster: test DataONE MN setup (need cross-signed cert) for:* SYNCHRONIZATION (aka HARVESTING) and* REPLICATIONCross-signing CA to update DataONE CA weak signature mechanism (nginx ingress)Ensure HTTP AUTHORIZATION Header handled correctly by nginx ingress (formerly Apache rewrite rule)Indexer**: add auth for solr access (indexer chart & metacat code)defer - not exposed outside clusterDEPLOY HELM ON DEV CLUSTERgetdataone_indexer
working a subcharttest auth for rabbitmq accessSupport DataONE Member Node Configuration when running in k8s #1662Mount secret (metacat container) for dataONE client certAllow setting non-default memory limits for tomcatFigure out how to do client side cert authentication via k8s ingress without apache mod-jkask ESS-DIVE if proposed setup serves their admin page and metacatui needsCreate Ingress (may solve some of the log/test issues)don't run webapp as rootusing secrets for passwordsdefining site properties overwriting behavior for new vs. existing helm deploymentsif path tometacat-site.properties
has been changed from the default, provide a helm-friendly way to avoid having to set it again via admin interface.Persistent Volume mounted atSolved - changed to/var/metacat
- working, but not poss to reconnect to same PV if Claim deleted when deployment deleted - so now creating claim only once, outside of deployment. Need to review with @mbjonesstatefulset
The text was updated successfully, but these errors were encountered: