Beyla in kubernetes detects itself as unknown_service:beyla

[gouthamve]

This is running with the following config:

  attributes:
    kubernetes:
      cluster_name: office
      enable: true
    select:
      beyla_network_flow_bytes:
        include:
        - k8s.src.owner.type
        - k8s.dst.owner.type
        - direction
  discovery:
    services:
    - k8s_namespace: .
  filter:
    network:
      k8s_dst_owner_name:
        not_match: '{kube*,*jaeger-agent*,*prometheus*,*promtail*,*grafana-agent*}'
      k8s_src_owner_name:
        not_match: '{kube*,*jaeger-agent*,*prometheus*,*promtail*,*grafana-agent*}'
  internal_metrics:
    prometheus:
      path: /internal/metrics
      port: 9090
  otel_traces_export:
    endpoint: http://k8s-monitoring-alloy.monitoring.svc.cluster.local:4317/
  prometheus_export:
    features:
    - application
    - network
    - application_service_graph
    - application_span
    path: /metrics
    port: 9090

[marctc]

hey @gouthamve, could you double check if you still have this issue? I definitively seen this before and I was trying to fix, but I can't see the issue anymore, so maybe the issue was fixed in recent versions?

[gouthamve]

I still see it with the latest :main

[marctc]

Could you verify which version is pulling? also which version of helm chart

[gouthamve]

helm chart: 1.7.2 , Beyla: revision="ee96e94"