-
Bug
-
Resolution: Done
-
Major
-
None
-
OpenShift 4.14 Async, OpenShift 4.13 Async, OpenShift 4.15 Async, OpenShift 4.16 Async
-
0
-
False
-
-
False
-
-
-
Important
- Pipelines are wrongly mentioned in the Advanced configuration options of Forwarding to Azure Monitor Logs sections.
- Here is the documentation link:
https://docs.openshift.com/container-platform/4.16/observability/logging/log_collection_forwarding/configuring-log-forwarding.html#logging-forwarding-azure_configuring-log-forwarding
- Here is the current Advanced configuration options part:
apiVersion: "logging.openshift.io/v1" kind: "ClusterLogForwarder" metadata: name: instance namespace: openshift-logging spec: outputs: - name: azure-monitor type: azureMonitor azureMonitor: customerId: my-customer-id logType: my_log_type azureResourceId: "/subscriptions/111111111" host: "ods.opinsights.azure.com" secret: name: my-secret pipelines: - name: app-pipeline <<== Wrong indentation inputRefs: - application outputRefs: - azure-monitor
- Due to this ClusterLogForwarder can not get applied. It streams the following errors:
Error parsing YAML: YAMLException: bad indentation of a sequence entry at line 19, column 5: inputRefs: Error parsing YAML: YAMLException: bad indentation of a sequence entry at line 20, column 5: - application Error parsing YAML: YAMLException: bad indentation of a sequence entry at line 21, column 5: outputRefs: Error parsing YAML: YAMLException: bad indentation of a sequence entry at line 22, column 5: - azure-monitor
- Here is the correct indentation:
apiVersion: "logging.openshift.io/v1" kind: "ClusterLogForwarder" metadata: name: instance namespace: openshift-logging spec: outputs: - name: azure-monitor type: azureMonitor azureMonitor: customerId: my-customer-id logType: my_log_type azureResourceId: "/subscriptions/111111111" host: "ods.opinsights.azure.com" secret: name: my-secret pipelines: - name: app-pipeline inputRefs: - application outputRefs: - azure-monitor
- I am raising a PR for this change and I will work on that PR.
