search

tricorder-observability / Starship

Starship: next-generation Observability platform built with eBPF+WASM
GNU Affero General Public License v3.0
163 stars 23 forks source link

[RFC] Removing non-ebpf-related capability out of Starship #254

Open nascentcore-eng opened 1 year ago

nascentcore-eng commented 1 year ago

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

nascentcore-eng commented 1 year ago

An example of reduced maintenance cost is in https://github.com/tricorder-observability/Starship/issues/258 where kube-prometheus-stack is broken on Kubernetes 1.25 and newer version because of the removal of pod security policy (PSP).