MONIT-40444: Pixie script changes for handling raw ebpf data and eBPF…

[zen10001]

This ticket is the pixie script changes for MONIT-40224 and MONIT-40568

Design document for a New Sampling Strategy for eBPF traffic(MONIT-40224) is here https://confluence.eng.vmware.com/pages/viewpage.action?spaceKey=WFENG&title=Design+Doc+for+a+New+Sampling+Strategy+for+eBPF+traffic

MONIT-40568 is for handling raw ebpf traffic in Application Topology. i.e. We no longer need to generate the synthetic parent span for pixie traffic, thus cutting the tracing data by half.

[oppegard]

@zen10001 we need to hold off on merging this since customers will be using the PxL script directly from main. We'll need to figure out the upgrade path (if any is needed), once MONIT-40224 and MONIT-40568 are available to the beta customers.

[zen10001]

@zen10001 we need to hold off on merging this since customers will be using the PxL script directly from main. We'll need to figure out the upgrade path (if any is needed), once MONIT-40224 and MONIT-40568 are available to the beta customers.

understand. won't merge into main until after beta release. Just for review and testing.

[oppegard]

@zen10001 we changed how we use PxL scripts since PR was opened. They're now deployed as K8s ConfigMaps (removing the need for the Pixie control plane to deploy PxL scripts):

• https://github.com/wavefrontHQ/observability-for-kubernetes/blob/main/operator/components/autotracing/cluster-spans-configmap.yaml
• https://github.com/wavefrontHQ/observability-for-kubernetes/blob/main/operator/components/autotracing/egress-spans-configmap.yaml
• https://github.com/wavefrontHQ/observability-for-kubernetes/blob/main/operator/components/autotracing/ingress-spans-configmap.yaml

Could you update the ConfigMaps with these changes, so this PR can remain the source of truth for when we eventually merge it?