agent-platform release v4.73.0

The model cache claim carries its tier: the hook that applies modelServing.cache.pvc stamps agent-platform.giantswarm.io/volume-type, -iops and -throughput (MiB/s) on it (giantswarm/agent-platform#605). The claim outlives its StorageClass by design — the chart’s class is Helm-owned and digest-named, so an uninstall or a parameter change removes it while the claim stays — and the class was the only place the volume’s tier could be read from, so cluster-manager answered “no price” for a claim that costs money. The annotations carry the EBS CSI class parameters type, iops and throughput: the chart’s own as rendered when the claim is on the class the chart renders, else what the claim’s class carries when the hook runs. They are written once, at create or on the first run that finds a claim without any of them while its class exists, and left alone afterwards; kubectl annotate writes them, not the claim’s apply, so no later apply removes them. A claim whose class is gone or that names none is not stamped, and the hook’s log says why. cluster-manager reads the tier from the annotations where the class is gone (giantswarm/cluster-manager#99). make verify-serving-slice asserts the stamped claim. README “The claim’s tier”.

The cache claim hook can read StorageClasses: get on storageclasses for <release>-hooks while the claim is the chart’s (giantswarm/agent-platform#605). The hook asked whether a Pending claim’s class still exists with an identity that could not read any class, so the check always answered “gone” and a Pending claim on a class the cluster has failed the hook. The same get reads the class parameters the claim’s tier is stamped from.