-
Notifications
You must be signed in to change notification settings - Fork 333
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
The current ingress only allows to expose the Polaris service, since the backend.service.name is "hardcoded" as the service name and port is set as the polaris service port. Seen the code snippet below
- host: {{ .host | quote }}
http:
paths:
{{- range .paths }}
- path: {{ .path }}
pathType: {{ .pathType }}
backend:
service:
name: {{ $fullName }}
port:
number: {{ $svcPort }}
This prevent user from exposing other backend services like the management service. We might want to allow user to expose additional services besides the core service.
To Reproduce
I want to configure the value.yaml to expose both polaris service and management service
ingress:
className: "somename"
enabled: true
hosts:
- host: chart-example.local
paths:
- path: /polaris
pathType: Prefix
backend:
service:
name: polaris-release
port: 8081
- path: /polaris-mgmt
pathType: Prefix
backend:
service:
name: polaris-release-mgmt
port: 8082
Actual Behavior
It would result as
- host: chart-example.local
http:
paths:
- path: /polaris
pathType: Prefix
backend:
service:
name: polaris-release
port:
number: 8181
- path: /polaris-mgmt
pathType: Prefix
backend:
service:
name: polaris-release
port:
number: 8181
Expected Behavior
- host: chart-example.local
http:
paths:
- path: /polaris
pathType: Prefix
backend:
service:
name: polaris-release
port:
number: 8181
- path: /polaris-mgmt
pathType: Prefix
backend:
service:
name: polaris-release-mgmt
port:
number: 8182
Additional context
No response
System information
OS: MacOS
Polaris version: 1.2.0
Storage: S3
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working