agent-platform release v4.44.0

Removed

• The classic KServe InferenceService serving path — llm-d is the one serving path. Breaking (giantswarm/agent-platform#574; the platform’s decision that no model is served on the classic vLLM path any more, no fallback, no deprecation window). The connectivity chart rendered two paths for a served model: the classic InferenceService on the chart’s kserve-vllm ClusterServingRuntime (modelServing.runtime, modelServing.additionalRuntimes, the classic predictor pod shape in the Kyverno policies, the network policies and the PolicyException, the serving.kserve.io/v1beta1 check behind kserve.requireApi, the runtime / runtimes keys of the discovery ConfigMap) and the llm-d path (LLMInferenceService on the well-known LLMInferenceServiceConfigs, the models Gateway), while every shipped preset was composed onto the llm-d template by model-manager. Now the chart renders no serving.kserve.io object at all: model-manager composes a published preset into an LLMInferenceService, and the serving namespace’s policies, network policies and exception select that workload pod alone (kserve.io/component=workload, app.kubernetes.io/part-of=llminferenceservice, container main, port 8000). Removed, and refused by the render naming the key: templates/model-serving/clusterservingruntime.yaml; the values modelServing.runtime, modelServing.additionalRuntimes (4.36.0, #550), modelServing.networkPolicy.predictor (its additionalIngressNamespaces is modelServing.networkPolicy.additionalIngressNamespaces), modelServing.serving.deploymentStrategyType and .timeoutSeconds; the preset fields spec.runtime and spec.predictor (the shipped qwen3-8-27b, qwen3-8-27b-l40s and qwen3-8-flash-next-nvfp4 lose their predictor.timeout, the Flash-Next preset its runtime: kserve-vllm-b12x — its B12X serving image is the well-known config’s to name); the discovery ConfigMap’s spec.runtime and spec.runtimes. modelServing.kserve.requireApi and modelManager.kserve.requireApi check serving.kserve.io/v1alpha2 (LLMInferenceService) and are satisfied by the kserve-llmisvc-crd + kserve-llmisvc-resources components. The meta chart drops the classic controller’s components kserve-crd and kserve-resources and their values blocks (refused too): kserve-llmisvc-crd ships every CRD the llm-d path needs (llminferenceservices, llminferenceserviceconfigs, clusterstoragecontainers), and the kserve-llmisvc-resources release renders the control plane’s shared objects itself (kserve.createSharedResources: true, the chart’s default; a false is refused) with controller.deploymentMode: Standard and gateway.disableIngressCreation: true, receives the derived models-Gateway reference (controller.gateway.ingressGateway.kserveGateway) and depends on kserve-llmisvc-crd alone; the connectivity release depends on no kserve component (it renders no serving.kserve.io CR), model-manager depends on kserve-llmisvc-resources and its range is >=0.23.0 <2.0.0 (model-manager 1.0.0 composes LLMInferenceServices only; nothing the chart forwards names the values it drops). examples/serving-slice.yaml, ci/test-slice-serving-values.yaml, the CI fixtures and the BOM switch the llm-d components on alone; tests/verify-runtimes.py, its fixture and the classic predictor pod fixture are gone, and verify-wiring asserts that the classic keys and components fail the render naming them and that the serving render carries no serving.kserve.io object. UPGRADE.md, “the classic KServe InferenceService path is removed”. Closes giantswarm/agent-platform#561 (removed with the feature).