apache / apache/apisix-helm-chart

This configuration may cause admin. allow_admin completely fails

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

Description

When .Values.ingress-controller.enabled or .Values.dashboard.enabled is true, an IP segment of 0.0.0.0/0 will be added by default. However, this 0.0.0.0/0 configuration will make all clients accessible, equivalent to admin.allow_admin configuration becomes invalid

![image](https://user-images.githubusercontent.com/12097229/231643597-dc7d6092-1b58-452d-a53c-7e22a7244bb3.png)

I think changing it to this would be okay

![image](https://user-images.githubusercontent.com/12097229/231644280-04d900a2-1729-49c6-bdc5-758339d883da.png)

After all, the internal IPs of K8S are all private IPs, and all you need to do is allow all IPs to access them

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the Helm templates or values that handle ingress-controller.enabled, dashboard.enabled, and admin.allow_admin. Reproduce the generated configuration with those settings enabled and inspect how 0.0.0.0/0 is added. Done means admin.allow_admin remains effective while the intended internal Kubernetes access still works; add or update chart validation if the repository provides it.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.