Krzysztof Słonka

consider using continuous profiling tools

5

### What happened? Consider using one of the continuous profiling tools instead of on-demand profiling: - https://github.com/profefe/profefe (storage: BadgerDB, S3, Google Cloud Storage and ClickHouse) - https://pyroscope.io/docs/golang/ (storage: [Grafana Pyroscope](https://github.com/grafana/pyroscope))

Add `--context` or similar to `kumactl`

5

### Description Make it possible to pick active control plane using a cli argument in `kumactl`. xref: https://github.com/kumahq/kuma/pull/7286

MeshHTTPRoute: capture a header value and use it in routing

5

### Description this would enable us to do dynamic routing based on header to preview environments - https://argo-cd.readthedocs.io/en/stable/operator-manual/applicationset/Generators-Pull-Request/ eg: header with: `x-preview-id: preview-123` would route to `kuma.io/service: service-preview-123_svc_8080`

Improve `AllowWithShadowDeny` (or/and RBAC in general)

4

### Description Right now `AllowWithShadowDeny` is not very useful due to the following: - ~RBAC filter being applied on the L4 level means that counter is only bumped on new...

### What happened? Reported via slack. ``` 2024-10-08T16:47:56.595Z INFO intercp.catalog.heartbeat could not send a heartbeat to a leader. It's likely due to leader change {"instanceId": "kuma-control-plane-6fd8cc445b-vzd77-a741", "ready": true, "leaderAddress": "X",...