v0.4.2

Added

• Ability to configure to not how SPIKE banner on startup.
• Ability to configure to show a warning if memory locking is not
  available on the system.
• SPIKE can now be deployed from SPIFFE helm charts. Tested and verified!
• Documentation updates.
• SPIKE Lite (a WIP SPIKE mode where you won’t need a backing store)
• SPIKE can be now be installed from SPIFFE Helm
  Charts and can
  federate secrets across clusters

Changed

• Moved logging to SPIKE SDK. VSecM v2 will share the same logging setup.
• spike policy command now accepts file input; you can design your policies
  as yaml files and then spike policy apply -f them.

Security

• Fixed GHSA-fv92-fjc5-jj9h: mapstructure May Leak Sensitive Information
  in Logs When Processing Malformed
  Data

---

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

What's Changed

• minor changes by @v0lkan in #168
• Disable banner via env config; disable memory warning via env config by @v0lkan in #169
• Docs and other things for the 4.1 prerelease. by @v0lkan in #170
• moved files around. by @v0lkan in #171
• Consume SPIKE from helm-charts-hardened by @v0lkan in #172
• minor changes to add clarity. by @v0lkan in #173
• Fix bare metal scripts by @rohatcan in #174
• fix orphaned spike processes by adding exec command to scripts by @rohatcan in #176
• WIP: (Potential) KubeCon Demo by @v0lkan in #175
• Add third edge cluster to demo. by @v0lkan in #180
• Using yaml file for policy creation by @parlakisik in #177
• introduce SPIKE Lite. by @v0lkan in #181
• Bump github.com/go-viper/mapstructure/v2 from 2.2.1 to 2.3.0 by @dependabot[bot] in #182
• Document: Update policy command with policy apply parameter by @parlakisik in #184
• Initial kind integration for spike by @parlakisik in #179
• Move logging to SDK by @v0lkan in #187
• SPIKE v0.4.2 by @v0lkan in #188

New Contributors

• @rohatcan made their first contribution in #174
• @parlakisik made their first contribution in #177

Full Changelog: v0.4.1...v0.4.2