agent-platform release v4.38.2

Fixed

• The serving namespace is kept on uninstall whatever the cache switch says, so a slice composed without the cache no longer deletes a cache claim an earlier slice left there (giantswarm/agent-platform#565). The connectivity chart put helm.sh/resource-policy: keep on the serving namespace only while modelServing.cache.enabled was on; a slice composed with the cache off rendered the namespace as an ordinary Helm-owned object, and its uninstall deleted the namespace — and with it the hf-cache claim an earlier slice (cache on) had applied there, the claim’s own keep policy notwithstanding (a namespace Helm deletes takes every object in it along). On an installation the claim was still Pending, so nothing was lost; a Bound claim’s volume (the class reclaims with Delete) would have gone, with the weights and compiled graphs on it. Now the namespace carries the policy whenever the chart creates it; the new modelServing.namespace.keep (default true) is the one way to the old behaviour — false renders the namespace without the policy, and the namespace and everything in it, a cache claim included, go with the release. The meta chart mirrors the block it forwards, and make verify-meta holds the two copies equal (tests/verify-mirrored-values.py). README “What an uninstall leaves behind” states the lifecycle in one paragraph, independent of the cache switch: the namespace outlives the release, the claim outlives the pool, and removing either is a person’s explicit act. make verify-serving-slice asserts the policy with the cache on and off and its absence with namespace.keep: false.