Skip to content

Replace logging component with a tutorial #15827

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

Closed
6 tasks done
a-thaler opened this issue Oct 17, 2022 · 4 comments
Closed
6 tasks done

Replace logging component with a tutorial #15827

a-thaler opened this issue Oct 17, 2022 · 4 comments
Labels
2023-Q3 Planned for Q3 2023 area/logging Issues or PRs related to the logging module (deprecated) Epic lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone

Comments

@a-thaler
Copy link
Contributor

a-thaler commented Oct 17, 2022

Description
Following the new Strategy, we don't want to offer a logging component fullfilling enterprise-grade quality as it would require bigger investment and will be always in conflict with solutions by other providers. Instead a well-done tutorial needs to be provided on how to install it on your own.

Actions:

Reasons
The focus of Kyma is not to provide Loki as an enterprise-grade managed offering as part of the cluster stack

Attachments

@a-thaler a-thaler added the 2023-Q2 Planned for Q2 2023 label Oct 19, 2022
@a-thaler a-thaler added 2023-Q3 Planned for Q3 2023 and removed 2023-Q2 Planned for Q2 2023 labels Dec 9, 2022
@kyma-bot
Copy link
Contributor

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

@kyma-bot kyma-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 18, 2023
@a-thaler a-thaler added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 20, 2023
@a-thaler
Copy link
Contributor Author

All is ready for the removal, now it is time to give users the chance to adopt first

@a-thaler a-thaler added this to the 2.16 milestone Jun 9, 2023
@a-thaler
Copy link
Contributor Author

a-thaler commented Jun 9, 2023

Removal is planned for 2.16

@Sawthis Sawthis modified the milestones: 2.16, 2.17 Jul 3, 2023
@a-thaler
Copy link
Contributor Author

a-thaler commented Jul 7, 2023

Actual removal is part of 2.17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2023-Q3 Planned for Q3 2023 area/logging Issues or PRs related to the logging module (deprecated) Epic lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

3 participants