Dataverse v4.17 on K8s
Pre-release
This release contains references to the upstream release 4.17 and will deploy it when used.
Pre-Deploy Actions
No special action seems to be necessary regarding to the upstream release docs.
Post-Deploy Actions
- The core bundled
citationmetadata block has changed. Simply follow the guide about "Metadata Blocks Job".
New and changed functionality
Docs
The documentation has been completly refactored, rewritten in Sphinx and massively extended. It contains almost everything from the old docs, some minor things still missing (like AWS deployment, detailed reuse tips, proper roadmap, ...)
The new guide lives at https://dataverse-k8s.rtfd.io
Solr deployment
We now replace rather than rollout in parallel due to locking issues. Those are completely avoidable now.
Metadata Schema Config in Solr
We inherit the upstream flexibility in configuring the Solr schema for indexing metadata fields. See the guide for how to use it.
New dev build cache
As Maven is downloading the internet when building Dataverse with our multistage build, a build cache has been split out. That way we can avoid the slow downloads of many packages and instead just download the small changes. The cache is updated every night to latest upstream develop branch.
Image documentation
The container images have their own doc section in the guide now. Those are also pushed to Docker Hub automatically on release with Jenkins.
Many things more.
See also milestone v4.17
General Notes
Please be aware that future enhancements to scripting and more used to deploy and configure Dataverse will not be added to the release. Thus docker images for this will not be updated.
Please be aware, that tagged images are not automatically updated by Kubernetes when updated on Docker Hub (image pull policy). See the guide for ideas.