The examples for enabling should be adjusted to correctly define the feature. "outputDefaults" applies to the default output only. This is a managed version of Elasticsearch offered by logging and referred to in CLF as "default". There is a similar functionality available for a defined instance of an Elasticsearch output, but the defaults do not "merge" into the customer defined instance. This is what is implied now.

For instance, the following example (in documentation) is correct for the default ES logstore that is defined in CL:

outputDefaults:
 elasticsearch:
    structuredTypeKey: kubernetes.labels.logFormat 
    structuredTypeName: nologformat
pipelines:
- inputRefs: <application>
  outputRefs: default
  parse: json

but further down the example listed here should be somethign like:

outputDefaults:
 elasticsearch:
    structuredTypeKey: kubernetes.labels.managed 
    structuredTypeName: nologformat
outputs:
- output:
  name: elasticsearch-secure
  elasticsearch:
    structuredTypeKey: openshift.labels.unmanaged 
    structuredTypeName: nologformat
pipelines:
 - name: application-logs
   inputRefs:
   - application
   - audit
   outputRefs:
   - elasticsearch-secure
   - default
   parse: json
   labels:
     myLabel: myValue

Where it is explicitly mentioned that "OutputDefaults" applies only to the default logstore and not other defined Elasticsearch outputs. Any place where we reference "default" in context of json parsing this is OK, otherwise we should include an example of an Elasticsearch output