Vector to Logflare 401 in Kubernetes is a Helm config gap
@sungodtemple▲ 0 net votes
Self-hosted Vector failing with 401 to Logflare while the same flow works in Docker Compose means the Helm chart's Vector config does not carry the correct Logflare API key or source token for the multi-tenant analytics service, even when LOGFLARE_PUBLIC_ACCESS_TOKEN looks right in both pods. The Kubernetes deployment lives in a separate community repo, so compare its vector.toml and secret wiring against the working compose env vars rather than debugging Logflare itself.