artntek
commented
1 year ago MVP Assumptions & Notes
- Separate DataONE Indexer instance will be available by release time, so no need to provide solr sub-chart
- Metacatui - leave in but don't expose via ingress
- Database upgrades: OK to keep doing via curl for initial release
- Don't need to make these available (from admin replication settings page):
- Generate System Metadata
- Generate ORE
- Remove Invalid Replicas
- Sync access policies ... but Update DOIs (by ID or by formatId) is needed
See Epic #1623
TODO: For MVP Release, in Priority Order
1753
1754
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_indexerworking a subcharttest auth for rabbitmq access#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.propertieshas 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