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 (#601). For logs the Loki output needs to get removed and the API prepared for OTLP support (#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:

• Preparations
  • Understand the k8s API restrictions and outline a path to a beta version (Path to a beta API version #712)
• Implementation
  • Align existing status API of logs and traces with syntactical kubernetes conventions (Align existing status API of logs and traces with syntactical kubernetes conventions #772)
  • Introduce new status API for logs and traces, mark the old one as deprecated (Introduce new status API for logs and traces, mark the old one as deprecated #805)
  • Prepare experimental beta feature: Introduce feature flag and adjust kustomize deployment to deploy dummy beta version only when active (Introduce beta API as experimental feature #848)
  • Remove old stats from traces and logs in beta version
  • Remove loki output from alpha and beta version ( Remove loki output #873)
  • Introduce conversion webhook for beta version (Introduce initial conversion webhook for beta version #1391)
  • Proper cert handling for conversion webhook
  • Switch to default handling via webhook to support namespaceSelector feature (Migrate // +kubebuilder:default annotations to a defaulting webhook #1541)
  • Implement namespaceSelector for alpha version (Determine system namespaces by label #380)
  • Adjust input section in logs beta version with conversion (namespace selector, enabled flag, naming) (LogPipeline Beta API #1395)
  • Migrate parts of ValidatingWebhook of LogPipeline which require CRD changes
    • Move API validation into CRD schema validation
  • Make sure that Go structs are properly named (e.g. LogPipeline specific types should be prefixed with LogPipeline, which is currently not the case)
  • Introduce beta API for operator
  • Do not promote LogParser
  • Switch the stored version, update all code to reference the new API and remove the feature flag
  • Unify Enabled vs Disabled flags in pipeline specs

[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: kyma-project/lifecycle-manager#1545

[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