-
Bug
-
Resolution: Done
-
Major
-
Logging 5.7.0
-
False
-
-
False
-
NEW
-
VERIFIED
-
Before this update, the plugin configuration defined in the Cluster Operator instance was not applied. With this update, the configuration is applied correctly.
-
-
Description: Seeing an error in logging-view-plugin pod after creating ConfigMap for logsLimit:
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-view-plugin-config
namespace: openshift-logging
labels:
app: logging-view-plugin
app.kubernetes.io/part-of: logging-view-plugin
data:
config.yaml: |-
logsLimit: 200
timeout: '60s'
error message in logging-view-plugin pod:
time="2023-04-06T09:59:01Z" level=warning msg="cannot read config file, serving plugin with default configuration, tried /etc/plugin/config.yaml" error="read /etc/plugin/config.yaml: is a directory" module=server
Here is how the configmap is mounted on the logging-view-plugin deployment:
spec:
containers:
- args:
- -plugin-config-path
- /etc/plugin/config.yaml
...
volumeMounts:
- mountPath: /var/serving-cert
name: serving-cert
readOnly: true
- mountPath: /etc/plugin/config.yaml
name: plugin-config
readOnly: true
...
volumes:
- name: serving-cert
secret:
defaultMode: 420
secretName: logging-view-plugin
- configMap:
defaultMode: 420
name: logging-view-plugin
optional: true
name: plugin-config
- links to
- mentioned on
