apache / apache/apisix-helm-chart

Helm chart apisix control ingress fails due to missing port.

Open
#798 1 comment 2 reactions 0 assignees View on GitHub
bug
Dominant language
Go Template
Stars
289
Forks
282
Avg merge
15h 55m
Merged PRs (30d)
3

Description

Error message:
> * Ingress.networking.k8s.io "apisix-control" is invalid: spec.rules[0].http.paths[0].backend: Required value: port name or number is required

There is an inconsistency between the values.yaml and the chart template.
- chart for ingress control is looking for the service Port via [`.Values.control.servicePort`](https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix/templates/ingress-control.yaml#L19)
- but values.yaml specifies that via (translated) [`.Values.control.service.servicePort`](https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix/values.yaml#L242)

Your decision which way it should be fixed/added/commented. Workaround is to define this value as `control.servicePort` in the custom values.yaml

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing charts/apisix/templates/ingress-control.yaml at line 19 with charts/apisix/values.yaml at line 242, focusing on the control service port path. Confirm the rendered control ingress no longer lacks a port and that the values structure and template reference are consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.