apache / apache/apisix-helm-chart
[Question] Why does APISIX require cluster-wide access to Kubernetes Secret resources?
Open
question
- Dominant language
- Go Template
- Stars
- 289
- Forks
- 282
- Avg merge
- 15h 55m
- Merged PRs (30d)
- 3
Description
https://github.com/apache/apisix-helm-chart/blob/7e5b8dff478dcc86373d6bd9071ab5444c97602b/charts/apisix-ingress-controller/templates/cluster_role.yaml#L17-L39
Contributor guide
No contributing guide indexed for this repository
Research direction
Read charts/apisix-ingress-controller/templates/cluster_role.yaml at lines 17-39 and inspect the Kubernetes Secret permissions defined there. Trace the ingress controller's secret-related entry points to determine whether cluster-wide access is required, then document the rationale or identify the narrower scope that would be sufficient.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- authorization, infrastructure
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100