Add LLMInferenceService support in models-web-appLICATION

[alokdangre]

Problem

KServe now has a first-class generative serving CRD, LLMInferenceService, but models-web-app only has first-class support for InferenceService and InferenceGraph.

This leaves LLM users dependent on kubectl for basic visibility into:

• model URI/name
• baseRefs composition
• single-node vs prefill/decode vs multi-node topology
• parallelism and scaling
• Gateway/HTTPRoute/Ingress exposure
• scheduler / InferencePool integration

Scope

• Add backend GET routes for:
  • list LLMInferenceService objects in one namespace
  • get single LLMInferenceService
  • get related events
• Add frontend types and service methods for LLMInferenceService
• Add routes/pages for:
  • list page
  • details page
• Surface at least:
  • name, namespace, ready state, URLs
  • model uri and name
  • baseRefs
  • topology summary:
    • single-node
    • multi-node (worker)
    • disaggregated (prefill)
  • parallelism
  • scaling / replicas
  • router mode:
    • managed route/gateway
    • BYO refs
    • scheduler enabled / disabled

Acceptance Criteria

• User can list LLMInferenceService resources in the selected namespace
• User can open a details page for a single LLMInferenceService
• Details page shows conditions and effective topology, not just raw YAML
• Implementation tolerates the current KServe dual-version reality (v1alpha1 and v1alpha2)
• Jest coverage added for types/status parsing and page rendering
• Cypress coverage added for list/details flows with mocked API responses

Follow up issue --> #176

[juliusvonkohout]

First the security must be fixed. Does it still require insecure/dangerous containers in kserve 0.17 ?

[alokdangre]

First the security must be fixed. Does it still require insecure/dangerous containers in kserve 0.17 ?

Sure, I have checked the security issue in kserve LLMInferenceService and I have suggested I fic in slack and asked the community about it
https://cloud-native.slack.com/archives/C06KZRPSDS7/p1774414718572329

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.