Align existing status API of logs and traces with syntactical kubernetes conventions #772
Labels
area/logs
LogPipeline
area/traces
TracePipeline
kind/feature
Categorizes issue or PR as related to a new feature.
Milestone
Description
As part of transitioning to a beta API the pipeline status needs to be aligned. Here the first step for it:
Status
,Message
) frommetav1.Condition
totelemetryv1alpha1.LogPipelineCondition
,telemetryv1alpha1.TracePipelineCondition
,telemetryv1alpha1.LogParserCondition
. However, define them as optional.Status
field in the CR-generated metricsReasons
Step number 1 described in https://github.com/kyma-project/telemetry-manager/blob/main/docs/contributor/arch/004-consolidate-pipeline-statuses.md
Attachments
Release Notes
The text was updated successfully, but these errors were encountered: