Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telemetry Beta API #767

Open
8 of 20 tasks
a-thaler opened this issue Feb 5, 2024 · 2 comments
Open
8 of 20 tasks

Telemetry Beta API #767

a-thaler opened this issue Feb 5, 2024 · 2 comments
Assignees
Labels
area/manager Manager or module changes kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@a-thaler
Copy link
Collaborator

a-thaler commented Feb 5, 2024

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:

@k15r
Copy link
Contributor

k15r commented May 15, 2024

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

Copy link

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 github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/manager Manager or module changes kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants