Skip to content

Dataverse v4.20 on K8s

Latest
Latest
Compare
Choose a tag to compare
@poikilotherm poikilotherm released this 23 Oct 14:23
v4.20
33b0695
This commit was created on GitHub.com and signed with GitHub鈥檚 verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

This release contains references to the upstream release 4.20 and will deploy it when used.

馃摉 The Cloud & Cointainer guide v4.20

馃攳 Pre-Deploy Actions

No special action seems to be necessary regarding to the upstream release docs.

馃摙 Post-Deploy Actions

  • You will need to adapt your storage configurations due to the new upstream feature of multiple storage locations.
    See upstream release notes for details and change your options accordingly.
  • The core bundled citation metadata block has changed. Simply follow the guide about "Metadata Blocks Job".

As always: Dataverse has release new functionality with this release. Be sure to read the upstream release notes, too.

馃巵 New and changed functionality

See also v4.20 milestone

  • Dataverse: support new multi storage location feature. See #196 and #195
  • Dataverse: update to v4.20. See #183
  • Guide: refactor to have a more streamlined usage experience for demo, development and production use. #160
  • Guide: add hints how to use with cloud providers. #108, #95
  • Personas: add a proof of concept docker-compose based demo option. #118
  • Personas: add an example how to use this project with an S3 compatible storage. #195, #51
  • Add Heap dump handler on OOM as a sidecar and provide loads of docs on memory usage. #204

馃悰 Bug fixes, 馃 workarounds and 馃 tweaks

  • Stop empty ConfigMaps when using kubectl apply. #194
  • Update tini in container image, making builds more stable. #187

馃 General Notes

Since this release, this project lives in the bosom of the big Global Dataverse Community Consortium family. (#199)
And we moved from the pattern of unstable master to a stable branch release and unstable branch develop, respecting inclusive language and streamlining with IQSS workflow for Dataverse. (#198)

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.

Assets 2