Fix named REST probe port in KServe runtime

[lusoris]

🛠 Summary

JIRA/Issue: N/A (external bug fix).

extras/kserve/kserve-openvino.yaml configures the startup probe with the
named port rest, but the container does not declare a port with that name.
Kubernetes resolves string probe ports against the container's named ports, so
the generated predictor pod cannot resolve rest.

Declare the REST container port as rest/TCP 8080. This matches the existing
--rest_port=8080 argument and lets the existing named startup probe resolve
without changing the server endpoint.

🧪 Checklist

• Unit tests added. Not applicable: this is a declarative manifest repair;
  the focused structural assertions below cover the broken contract.
• The documentation updated. Not applicable: no user-facing behavior or
  option changes.
• Change follows security best practices.

Validation:

• Parsed the manifest with PyYAML.
• Validated it against the KServe v0.20.0 ClusterServingRuntime OpenAPI
  schema.
• Asserted that startupProbe.httpGet.port resolves to exactly one declared
  container port and that its value, 8080, matches --rest_port=8080.
• git diff --check.

[Copilot]

Pull request overview

Fixes a KServe ClusterServingRuntime manifest contract issue where the startup probe references a named port (rest) that was not declared on the container, preventing Kubernetes from resolving the probe port.

Changes:

• Declares the REST container port as a named port rest on TCP/8080 to match --rest_port=8080.
• Keeps the existing startup probe configuration intact by making the port reference resolvable.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.