vguddoda opened a new issue, #12281:
URL: https://github.com/apache/apisix/issues/12281
### Current Behavior
When mounting a ConfigMap containing config.yaml into the APISIX Control
Plane container using volumeMounts, APISIX startup fails with an error
indicating that the file /usr/local/apisix/conf/config.yaml has write
permissions.
volumeMounts:
- name: config
mountPath: /usr/local/apisix/conf/config.yaml
subPath: config.yaml
sample configmap
apiVersion: v1
kind: ConfigMap
metadata:
name: {{ include "data-plane.name" . }}-config
namespace: {{ .Release.Namespace }}
data:
config.yaml: |
deployment:
role: {{ .Values.apisix.deploymentRole }}
role_data_plane:
config_provider: {{ .Values.apisix.configProvider }}
apisix:
node_listen: {{ .Values.apisix.nodePort }}
enable_admin: {{ .Values.apisix.enableAdmin }}
enable_heartbeat: {{ .Values.apisix.enableHeartbeat }}
enable_report: {{ .Values.apisix.enableReport }}
enable_debug: {{ .Values.apisix.enableDebug }}
### Expected Behavior
There should be way if we mount configyaml using volumeMount , control plane
should come up.
### Error Logs
_No response_
### Steps to Reproduce
Add
volumeMounts:
- name: config
mountPath: /usr/local/apisix/conf/config.yaml
subPath: config.yaml
configmap
sample configmap
apiVersion: v1
kind: ConfigMap
metadata:
name: {{ include "data-plane.name" . }}-config
namespace: {{ .Release.Namespace }}
data:
config.yaml: |
deployment:
role: {{ .Values.apisix.deploymentRole }}
role_data_plane:
config_provider: {{ .Values.apisix.configProvider }}
apisix:
node_listen: {{ .Values.apisix.nodePort }}
enable_admin: {{ .Values.apisix.enableAdmin }}
enable_heartbeat: {{ .Values.apisix.enableHeartbeat }}
enable_report: {{ .Values.apisix.enableReport }}
enable_debug: {{ .Values.apisix.enableDebug }}
### Environment
3.12 latest APISIX version as of today.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
