Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add pathTemplate field to values.yaml for increased flexibility of helm chart #4237

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

DeepFlame-JR
Copy link

What this PR does / why we need it:

  • I needed to set the pathTemplate value while installing via helm chart, but it didn't exist.
  • I just add the pathTemplate in helm chart.

Which issue(s) this PR fixes

Type of changes

  • This change requires a documentation update

Release note:

NONE

@@ -273,7 +274,7 @@ data:
# Namespace of the inference service ( {{- "{{ .Namespace }}" -}} )
# For more info https://github.com/kserve/kserve/issues/2257.
# NOTE: This configuration only applicable to serverless deployment.
"pathTemplate": "/serving/{{ .Namespace }}/{{ .Name }}"
"pathTemplate": ""
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO this is just an example that shows how to use the placeholders, and can stay unchanged. The previous block where you added this field should be enough to show what is the default value.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think can keep it as example for reference.

@@ -154,6 +154,9 @@ kserve:
# -- Ingress domain template for RawDeployment mode, for Serverless mode it is configured in Knative.
domainTemplate: "{{ .Name }}-{{ .Namespace }}.{{ .IngressDomain }}"

# -- Path template for RawDeployment mode, for Serverless mode it is configured in Knative.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused, because the comments of the configmap.yaml that you also changed tell this field is for Serverless. But, here, you say it is for Raw. Either, here is wrong, or configmap.yaml is wrong.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DeepFlame-JR path based routing is supported in both serverless and raw deployment (with gateway api).

@lizzzcai
Copy link
Member

Hi @DeepFlame-JR can you sign off your commit

@DeepFlame-JR
Copy link
Author

@lizzzcai @israel-hdez @sivanantha321
Can you please check the changes?

@@ -272,7 +273,7 @@ data:
# Name of the inference service ( {{- "{{ .Name }}" -}} )
# Namespace of the inference service ( {{- "{{ .Namespace }}" -}} )
# For more info https://github.com/kserve/kserve/issues/2257.
# NOTE: This configuration only applicable to serverless deployment.
# If path template is empty the default path template is ""
Copy link
Member

@sivanantha321 sivanantha321 Feb 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this line is confusing. It should be something like If the path template is an empty string "" then path based routing is disabled.

@@ -154,6 +154,9 @@ kserve:
# -- Ingress domain template for RawDeployment mode, for Serverless mode it is configured in Knative.
domainTemplate: "{{ .Name }}-{{ .Namespace }}.{{ .IngressDomain }}"

# -- Path template for RawDeployment mode, for Serverless mode it is configured in Knative.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# -- Path template for RawDeployment mode, for Serverless mode it is configured in Knative.
# -- pathTemplate specifies the template for generating path based url for each inference service. If the value is an empty string, then path based routing will be disabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants