Skip to content

feat: make epp-standalone be its own chart#2122

Merged
k8s-ci-robot merged 12 commits intokubernetes-sigs:mainfrom
capri-xiyue:capri-xiyue/refactor-using-library-chart
Jan 12, 2026
Merged

feat: make epp-standalone be its own chart#2122
k8s-ci-robot merged 12 commits intokubernetes-sigs:mainfrom
capri-xiyue:capri-xiyue/refactor-using-library-chart

Conversation

@capri-xiyue
Copy link
Copy Markdown
Contributor

@capri-xiyue capri-xiyue commented Jan 12, 2026

What type of PR is this?

/kind feature
What this PR does / why we need it:
Enable users to install epp-standalone mode via helm chart
I made inference-extension be a library chart
Bothepp-standalone and inferencepool will call inference-extension library chart.

In short,

  • moved all epp-related resources into config/charts/inference-extension
  • config/charts/epp-standalone be a application chart used to deploy epp-standalone mode
  • config/charts/inferencepool with user face not changed.
  • refactorconfig/charts/inferencepool/templates/rbac.yaml to be config/charts/inferencepool/templates/rbac.yaml and config/charts/epp-standalone/templates/epp-rbac.yaml as some rbac is for inferencepool and some rbac is for epp
  • refactorconfig/charts/inferencepool/templates/gke.yaml to be config/charts/inferencepool/templates/rbac.yaml and config/charts/epp-standalone/templates/epp-gke.yaml as some gke set up is for inferencepool and some rbac is for epp

See #2063
Which issue(s) this PR fixes:

Fixes #2063

Does this PR introduce a user-facing change?:
Users can install epp standalone via

helm install vllm-llama3-8b-instruct-standalone ./config/charts/epp-standalone \
  --set inferenceExtension.endpointsServer.endpointSelector="app=vllm-llama3-8b-instruct" \
  --set provider.name=gke 

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 12, 2026
@netlify
Copy link
Copy Markdown

netlify bot commented Jan 12, 2026

Deploy Preview for gateway-api-inference-extension ready!

Name Link
🔨 Latest commit e115a98
🔍 Latest deploy log https://app.netlify.com/projects/gateway-api-inference-extension/deploys/69655d71c4ed9b0008ab88fe
😎 Deploy Preview https://deploy-preview-2122--gateway-api-inference-extension.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jan 12, 2026
@capri-xiyue
Copy link
Copy Markdown
Contributor Author

assign @ahg-g

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 12, 2026
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 12, 2026
Signed-off-by: Xiyue Yu <xiyue@google.com>
@capri-xiyue capri-xiyue requested a review from ahg-g January 12, 2026 18:33
Signed-off-by: Xiyue Yu <xiyue@google.com>
@capri-xiyue
Copy link
Copy Markdown
Contributor Author

/retest

@capri-xiyue capri-xiyue requested a review from ahg-g January 12, 2026 21:22
@ahg-g
Copy link
Copy Markdown
Contributor

ahg-g commented Jan 12, 2026

This is an amazing refactor!

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 12, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahg-g, capri-xiyue

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 12, 2026
@k8s-ci-robot k8s-ci-robot merged commit a4f971f into kubernetes-sigs:main Jan 12, 2026
11 checks passed
@nirrozenbaum
Copy link
Copy Markdown
Contributor

@capri-xiyue out of curiosity, do we need all these template files, each with a single line of include statement?
or could it be implemented in a single template file, e.g., inference-extension.yaml where it's content would be all the include statements with a separator?
e.g., something like:

{{- include "inference-extension.config" . -}}
---
{{- include "inference-extension.deployment" . -}}
---
{{- include "inference-extension.gke" . -}}
...
...

@capri-xiyue
Copy link
Copy Markdown
Contributor Author

@capri-xiyue out of curiosity, do we need all these template files, each with a single line of include statement? or could it be implemented in a single template file, e.g., inference-extension.yaml where it's content would be all the include statements with a separator? e.g., something like:

{{- include "inference-extension.config" . -}}
---
{{- include "inference-extension.deployment" . -}}
---
{{- include "inference-extension.gke" . -}}
...
...

@nirrozenbaum I will try how one yaml include works for me or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Standalone] refactor epp outside of existing inference pool helm chart

4 participants