Telemetry Beta API

[a-thaler]

Description The telemetry API should head towards a proper v1 version and requires the step to a beta version as next step. For the logs and trace API, smaller things should get adjusted like changing the status to be conform to k8s conventions (https://github.com/kyma-project/telemetry-manager/issues/601). For logs the Loki output needs to get removed and the API prepared for OTLP support (https://github.com/kyma-project/telemetry-manager/issues/556).

The goal is to get a streamlined API across all pipeline types with a betaV1 version, having:

• consistent status handling
• consistent OTLP output handling
• consistent input handling

Action:

• [x] Preparations
  • [X] Understand the k8s API restrictions and outline a path to a beta version (https://github.com/kyma-project/telemetry-manager/issues/712)
• [ ] Implementation
  • [x] Align existing status API of logs and traces with syntactical kubernetes conventions (https://github.com/kyma-project/telemetry-manager/issues/772)
  • [x] Introduce new status API for logs and traces, mark the old one as deprecated (https://github.com/kyma-project/telemetry-manager/issues/805)
  • [x] Prepare experimental beta feature: Introduce feature flag and adjust kustomize deployment to deploy dummy beta version only when active (https://github.com/kyma-project/telemetry-manager/issues/848)
  • [ ] Introduce beta API for operator
  • [ ] Remove loki output from logs beta version (https://github.com/kyma-project/telemetry-manager/issues/873)
  • [ ] Introduce conversion webhook for beta version (https://github.com/kyma-project/telemetry-manager/issues/873)
  • [ ] Adjust input section in logs beta version (namespace selector, enabled flag, naming)
  • [ ] Migrate parts of ValidatingWebhook of LogPipeline which require CRD changes
    • [ ] Move API validation into CRD schema validation
    • [ ] Move unsupported mode warning
  • [ ] Remove old stats from traces and logs in beta version
  • [ ] Remove LogParser https://github.com/kyma-project/telemetry-manager/issues/823
  • [ ] Remove feature flag
  • [ ] Make sure that Go structs are properly named (e.g. LogPipeline specific types should be prefixed with LogPipeline, which is currently not the case)
• Follow-Ups
  • [ ] Switch to namespace selector by labels (https://github.com/kyma-project/telemetry-manager/issues/380)
  • [ ] Remove ValidatingWebhook of LogPipeline
    • [ ] Max Pipeline check to be executed on backend side similar to TracePipeline, having proper status change
    • [ ] Singleton check for telemetry resource https://github.com/kyma-project/telemetry-manager/issues/555
    • [ ] Plugin validation with supported list and hardcoded available plugin list as backend validation feature reflected via status change
    • [ ] Missing file/variable reference validation
    • [ ] Delete dry-run and get manager image free (https://github.com/kyma-project/telemetry-manager/issues/1234)
    • [ ] Delete webhook

[k15r]

Important for the removal of the old crd version

• create a script to update all existing CRs to the latest version (read it from API-Server, write it back in the latest version)
• mark the old version as served: false, storage: false
• remove the old version from the Status Subressource of the CRD status.storedVersions
• remove the old version from the spec of the CR

keep track of this issue: https://github.com/kyma-project/lifecycle-manager/issues/1545