v0.4.1

Added

• Initial support for Kubernetes deployments.
• Better shard sanitization during recovery procedures.
• Added memory locking to SPIKE Pilot too.
• Finer control of the startup script via flags.
• Added the ability to optionally skip database schema creation during SPIKE
  initialization.

Changed

• BREAKING: SDK validation methods now take trust root as an argument.
• BREAKING: SPIKE_NEXUS_KEEPER_URL is now a comma-delimited list of URLs
  (instead of JSON).
• SPIKE components can now be configured to accept multiple trust roots as
  legitimate peers---this will be useful in complex mesh and federation
  deployment scenarios.
• SPIKE now uses GitHub Container Registry to store its container image
  (instead of Docker Hub).

---

Below are the generated release notes of every commit since the last release cut:

What's Changed

• Project Status Change. by @v0lkan in #130
• Store state from backing store immediately after doomsday recovery. by @v0lkan in #131
• restoration files are hex encoded now. by @v0lkan in #132
• Stricter pattern matching for Secret and Policy Operations by @v0lkan in #143
• Ability to accept multiple trust roots. by @v0lkan in #144
• KEEPER_URL format change. by @v0lkan in #145
• option to skip db schema initialization. by @v0lkan in #148
• Log keeper warning to stderr by @kfox1111 in #155
• Fix containers by @kfox1111 in #156
• spike secret get format by @kfox1111 in #157
• Containerization by @v0lkan in #165
• Fix workflow after merge by @kfox1111 in #167

New Contributors

• @kfox1111 made their first contribution in #155

Full Changelog: v0.4.0...v0.4.1