Dataverse v4.15 on K8s

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

Pre-Deploy Actions

You might need to fix your users. Quoting from upstream release docs:

• In an effort to prevent accidental duplicate accounts, user spoofing, or other username-based confusion, this release introduces a database constraint that no longer allows usernames that are exactly the same but use different capitalization, e.g. Bob11 vs. bob11. You may need to do some cleanup before upgrading to deal with existing usernames like this.
• To check whether you have any usernames like this that need cleaning up, run the case insensitive duplicate queries from our Useful Queries doc.
• Once you identify the usernames that need cleaning up, you should use either Merge User Accounts (if it’s the same person) or Change User Identifier (if they are different people). After the cleanup you can safely upgrade without issue.

Post-Deploy Actions

• The Solr Schema changed, so you should do an inplace reindex.
  Have a look at the docs to learn how to do this within your K8s cluster easily.

None the less, please take a look at the rest of upstream release notes, too.

Notes:

• You don't need to deal with jhove.conf, this is done at container build time. Just deploy.
• Don't worry about the optional replacing of solrconfig.xml. Not necessary and would have been done at container build time.

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.

This is especially important in terms of security patches for images. This might change in the future with scheduled builds from CI.

Please be aware, that tagged images are not automatically updated by Kubernetes when updated on Docker Hub (image pull policy).