v0.14.1

Upgrading compute no longer recreates running instances whose workload is unchanged.

What's new

• Instances keep running across upgrades. v0.14.0 recreated every instance that mounts a ConfigMap or Secret volume because the Kubernetes 0.37 libraries changed how its template hashed. The template hash now ignores unset fields, and instances carrying the older hash count as current and have it rewritten in place. (#561)

Note

No schema changes. Existing resources keep working without any conversion. Upgrading from v0.14.0 recreates no instances; staging upgraded from the same libraries with no instance recreated. An instance still carrying a v0.13.3 hash is recreated once.

Changelog

• 5d871cf Merge pull request #561 from datum-cloud/fix/560-stable-template-hash
• 5cd41d4 fix: Continue the reconcile when a hash rewrite fails
• 74a1dde fix: Keep instances running across library upgrades