agent-platform release v4.73.2

Fixed

• Switching the serving slice off, or uninstalling a release that carries it, no longer leaves kserve-runtime-configs UninstallFailed or its configs terminating (giantswarm/agent-platform#527). The llm-d controller (kserve-llmisvc-resources) puts serving.kserve.io/llmisvcconfig-finalizer on every well-known LLMInferenceServiceConfig, is the only thing that clears it, and its webhook denies every delete of such a config while it runs; Helm deleted both child HelmReleases in one pass, so the configs’ uninstall was denied, or the configs were left terminating for the next slice to adopt and lose (ConfigNotFound). A hook Job <release>-serving-teardown (weight -2, the helm image, as <release>-hooks, with the engine and without it) now removes them in order: the controller’s release, waited for until its Deployment and the webhook configuration are gone; the configs of kserve-runtime-configs, deleted through the CRD’s storage version with the finalizer taken off; then the configs’ release. It runs at pre-delete while both components are on, and at pre-upgrade when components.kserve-runtime-configs goes off while its live HelmRelease is the release’s (a lookup). Switching kserve-runtime-configs off while kserve-llmisvc-resources stays on is refused with the reason. Not with gitops.target.kubeConfig: cluster-manager tears its slices down in this order itself. make verify-serving-teardown asserts the renders and runs the script against a stub kubectl. README “Uninstalling”.