help request: apisix file-standalone mode config apisix.yaml path
- Dominant language
- Lua
- Stars
- 17.1k
- Forks
- 2.9k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 63
Description
### Description
How to customize the default path of apisix.yaml/apisix.json via args or env vars for K8s hot reload?
I am currently deploying APISIX in a Kubernetes environment using Standalone mode, and I mount the configuration files via K8s volumes.
My goal is to enable hot reloading for the configuration. However, it seems this isn't working as expected, and I suspect it might be related to the file path.
Could you please advise on how to change the default path of apisix.yaml or apisix.json? Specifically, is there a way to override this default path using startup arguments or environment variables?
Any guidance or best practices for achieving file hot reload in K8s would be greatly appreciated.
### Environment
- APISIX version (run `apisix version`): apache/apisix:3.16.0
- Operating system (run `uname -a`):
- OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
- etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`): file
- APISIX Dashboard version, if relevant:
- Plugin runner version, for issues related to plugin runners:
- LuaRocks version, for installation issues (run `luarocks --version`):
Contributor guide
Research direction
Start by checking the APISIX standalone-mode configuration entry points for apisix.yaml and apisix.json, along with how Kubernetes volumes are mounted. Confirm whether startup arguments or environment variables can override the path and whether mounted-file changes trigger hot reload; document the supported configuration or the specific missing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100