apache / apache/apisix-helm-chart
Apisix Control Ingress - servicePort variable misplaced in templates/ingress-control.yaml
- Dominant language
- Go Template
- Stars
- 289
- Forks
- 282
- Avg merge
- 15h 55m
- Merged PRs (30d)
- 3
Description
Helm Chart Version: 2.10
Apisix Version: 3.11
Considering the example values.yaml, one would assume that control.service.servicePort is the port used for Control Ingress, however the templates/ingress-control.yaml expects the variable at control.servicePort.
{{- $svcPort := .Values.control.servicePort -}}
Suggested change:
Edit ingress-control.yaml to match the placement of control.service.servicePort:
{{- $svcPort := .Values.control.service.servicePort -}}
Temporary workaround I used:
Just define servicePort at control.servicePort
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the control.service.servicePort path in values.yaml with the lookup in templates/ingress-control.yaml. Render the chart using the example values and verify that Control Ingress uses the configured service port without requiring the workaround path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100