Add KServe support with vLLM backend and Ansible integration #48
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds Kubernetes-native model serving via KServe with vLLM runtime, providing serverless inference, autoscaling, and canary deployment capabilities for Intel Xeon and Gaudi platforms.
Implementation
Helm Chart (
core/helm-charts/kserve/)xeon-values.yaml(pipeline parallelism),gaudi-values.yaml/gaudi3-values.yaml(tensor parallelism, bfloat16)Ansible Playbooks
deploy-kserve-operator.yml: Installs KServe v0.13.0 CRDs/controller, creates Intel-optimized ClusterServingRuntimesdeploy-kserve-models.yml: Helm-based model deployment with platform detection, HuggingFace token validation, proper cleanup with k8s_info pollingConfiguration
inventory/metadata/vars/inference_kserve.yml: 60+ variables (platform selection, autoscaling, storage, model-specific args)inventory/inference-config.cfg: Addeddeploy_kserve_operator,deploy_kserve_models,uninstall_kserveflagsdocs/examples/kserve/for Xeon and Gaudi deploymentsIntegration Points
helm_charts_base,remote_helm_charts_basefrom current playbook patternsUsage
Key Configurations
Xeon: 16-32 cores, 64-128GB RAM, AVX512 node selector, pipeline parallelism enabled
Gaudi: 1 accelerator, 128-256GB RAM, enforce-eager mode, bfloat16 precision
Gaudi3: 1 accelerator, 256-512GB RAM, 16K context length support
Documentation
docs/kserve-deployment-guide.md: Architecture, deployment steps, troubleshootingdocs/examples/kserve/QUICKSTART.md: 5-minute setup guidecore/helm-charts/kserve/README.md: Technical implementation detailsNotes
k8s_infopolling instead of fixed delays for reliable cleanupOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.