You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a meaningful suggestion, but few users would do this, especially in a k8s cluster. Supporting such a feature would require users to ensure correct configuration on their own, which could introduce risks.
It's a meaningful suggestion, but few users would do this, especially in a k8s cluster. Supporting such a feature would require users to ensure correct configuration on their own, which could introduce risks.
Isn't it the idea on standalone mode, that you can edit this file? Now it is not possible to use standalone mode on kubernetes (with this helm chart) because you cannot actually add any configuration there. Unless if you are fine with editing the configmap straight on the cluster.
For example, I would like to have this configuration stored in git repository which I use for deployment. But currently it is impossible.
I have created a pull request with related changes. The pull request allows to override content of the apisix.yaml ConfigMap or to use existing ConfigMap.
Meanwhile you can use either branch dev or more-standalone-config-options from https://github.com/jompu/apisix-helm-chart to install modified version of the APISIX 2.6.0 chart.
When using APISIX standalone mode as a subchart, 'apisix.yaml' configmap is always re-initialized when upgrading the parent chart.
I think using an external configmap as the "apisix.yaml" is a simple solution for solving them!
Example: (variable names and paths are very sensitive part of the project, so this code is just a sample!)
apisix-config-configmap.yaml:
_pod.tpl:
values.yaml:
Maybe this feature will also be very helpful for other APISIX users :)
The text was updated successfully, but these errors were encountered: