LogPipeline Beta API

[a-thaler]

Description

With #767 the LogPipeline will be promoted to a beta API. For that, the API of the input section needs to get aligned with the Trace/MetricPipeline APIs. The filter and output sections will stay as they are as they will be faded out together with the fluentbit fade out.

Old API:

input:
  application:
    dropLabels: false
    keepAnnotations: false
    keepOriginalBody: true
    containers: # mutually exclusive
      exclude:
        - ns1
        - ns2
      include:
        - ns3
        - ns4
    namespaces: # mutually exclusive
      system: true
      exclude:
        - ns1
        - ns2
      include:
        - ns3
        - ns4

New API propsal:

input:
  runtime:
    enabled: true # if false, no configuration gets generated. With OTLP, a false value will run the gateway only
    dropLabels: false # stays as is. With OTLP, a new replacement "podLabels" will be added, specifying a list of pod labels to add
    keepAnnotations: false # stays as is. With OTLP, a new replacement "podAnnotations" will be added, specifying a list of pod annotations to add
    keepOriginalBody: true # stays as is
    containers: # stays as is
      exclude:
        - ns1
        - ns2
      include:
        - ns3
        - ns4
    namespaceSelector: #either expression or label. By default an expression gets generated excluding kyma namespaces
        matchExpressions:
        - key: namespace
          operator: In
          values: ["frontend", "backend"]
       matchLabels:
          role: backend

Criterias

• The LogPipeline beta API will leverage the new input API
• The beta API stays compatible to alpha via the conversion webhook

Reasons

Attachments

Release Notes

[github-actions]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

[github-actions]

This issue has been automatically closed due to the lack of recent activity.
/lifecycle rotten