Skip to content
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

Unable to enrich the data with Kubernetes Metadata on K3s #100

Open
VishwasSomasekhariah opened this issue Feb 1, 2023 · 0 comments
Open
Labels
bug Something isn't working

Comments

@VishwasSomasekhariah
Copy link

Indicate project
Collector

Describe the bug
On trying to enrich the eBPF data with Kubernetes metadata, received an error fetching K8s Data

To reproduce
Steps to reproduce the behavior:

  1. Deployed Vanilla sysflow with sf-processor.
  2. Added clusterrole with name sysflow-agent
  3. Added clusterrolebinding with name sysflow-agent
  4. Edited daemonset.yaml, adding env in sfcollector container:
            - name: SF_K8S_API_URL
              value: https://kubernetes.default.svc/
            - name: SF_K8S_API_CERT
              value: /var/run/secrets/kubernetes.io/serviceaccount/token

Expected behavior
Should have enriched the Raw eBPF data with Kubernetes metadata (namespace, pod details etc)

Screenshots
image

Environment (please complete the following information):

  • OS: Ubuntu 20.04.5 LTS
  • SysFlow version: v0.5.0
  • Container orchestration framework and version (if applicable): Civo K3s v1.22.11+k3s1
  • Container runtime (if applicable): containerd://1.5.13-k3s1

Additional context
I verified that the node name represented by EXPORTER_ID in the sf-collector container is correct and present in my cluster.

@VishwasSomasekhariah VishwasSomasekhariah added the bug Something isn't working label Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant