Enable custom ingress path for ALB in Helm chart #72
Description
Hello 👋
First of all, thank you for providing this Helm chart—it’s been extremely helpful!
I’m currently trying to use AWS ALB Ingress instead of NGINX. However, when I install the chart with the following values.yaml, I encounter this error:
Warning FailedDeployModel 15m ingress
Failed deploy model due to ValidationError: Condition value '/(.*)'
contains a character that is not valid
status code: 400, request id: 10e0a179-9ac2-4524-8cd9-655c7f33f203Currently, the Helm chart’s rules block hard-codes the path and doesn’t allow customization:
rules:
- host: {{ .Values.hyperdx.ingress.host | default "localhost" }}
http:
paths:
- path: /(.*)
pathType: ImplementationSpecific
backend:
service:
name: {{ include "hdx-oss.fullname" . }}-app
port:
number: {{ .Values.hyperdx.appPort }}To support AWS ALB users, would it be possible to make the path field configurable via values.yaml? For example, changing that section to:
rules:
- host: {{ .Values.hyperdx.ingress.host | default "localhost" }}
http:
paths:
- path: {{ .Values.hyperdx.ingress.path | default "/(.*)" }}
pathType: ImplementationSpecific
backend:
service:
name: {{ include "hdx-oss.fullname" . }}-app
port:
number: {{ .Values.hyperdx.appPort }}I believe adding a ingress.path value would greatly benefit users who need custom routing patterns. Thank you for considering this enhancement!
Chart: hdx-oss-v2-0.6.5
appVersion: 2.0.1