[RFC] Removing non-ebpf-related capability out of Starship #254
Labels
community
Open Source community surrounding Starship and Tricorder project
needs-triage
Newly created issues that need assessment and find appropriate assignee
rfc
Request For Comments, proposals for community and team members to comment
What's the motivation? Is it related to a problem?
Starship is designed with eBPF as it's core and foundation.
We have components like kube Prometheus stack to support mainstream observability capability.
This is wrong, as we are not going to win customers with those table stake capabilities like prom and otel, and supporting those features consume quite a lot of man power. For example, we have 1 part time team member dedicated to maintaining the helm charts for bundling prom and otel components in Starship.
Describe the proposal
Removing prom and otel support from helm charts, leave only the eBPF related components.
Describe alternatives you've considered
Continue maintaining prom and otel components.
Additional context, for example, related issues, Kubernetes versions, Kernel versions etc.
None
The text was updated successfully, but these errors were encountered: