Before this update, any namespace containing "openshift" or "kube" was classified as an infrastructure namespace. Following this update, only the following namespaces are classified as infrastructure namespaces: "default", "kube", "openshift", and namespaces starting with "openshift-" or "kube-".

1) Deploy Logging Operator 2) Creating a SA and a cluster rolebinding to deploy the multiCLF instance $ oc -n openshift-logging create serviceaccount vector2vector-log-forwarder $ oc create clusterrolebinding vector2vector-log-forwarder --clusterrole=collect-application-logs --serviceaccount openshift-logging:vector2vector-log-forwarder 3) Deploy a multiCLF with a namespace that contains kube or openshift: spec: inputs: - application: namespaces: - sample-kube-example name: test-input outputs: - name: test-output type: http url: https: //test.com:1900 pipelines: - inputRefs: - test-input name: test-pipeline outputRefs: - test-output serviceAccountName: vector2vector-log-forwarder status: conditions: - lastTransitionTime: "2024-09-09T13:59:22Z" reason: ValidationFailure status: "False" type: Ready - lastTransitionTime: "2024-09-09T13:59:22Z" message: insufficient permissions on service account, not authorized to collect [ "infrastructure" ] logs reason: ValidationFailure status: "True" type: Validation 4) The collector interprets from the namespace that they are infra logs so we can do the following workaround: $ oc create clusterrolebinding vector2vector-log-forwarder-infra --clusterrole=collect-infrastructure-logs --serviceaccount openshift-logging:vector2vector-log-forwarder 5) After that, a couple of minutes later we don´t find any issues in the multiCLF apiVersion: logging.openshift.io/v1 kind: ClusterLogForwarder metadata: creationTimestamp: "2024-09-09T13:59:22Z" generation: 2 name: test-clf namespace: openshift-logging resourceVersion: "90685" uid: a2026d1c-b183-4c83-9a5f-22d09c8d9e1b spec: inputs: - application: namespaces: - sample-kube-example name: test-input outputs: - name: test-output type: http url: https: //test.com:1900 pipelines: - inputRefs: - test-input name: test-pipeline outputRefs: - test-output serviceAccountName: vector2vector-log-forwarder status: conditions: - lastTransitionTime: "2024-09-09T14:09:22Z" status: "True" type: Ready