What happened:
Static pods export traces to our tracing backend. While this might be useful in later iterations, we are not interested in these traces in our current version.
What you expected to happen:
I expect these traces to not be exported into out backend.
How to address
There are Kubelet methods that deal with this, and we could hook some logic in here, but it might not be worth doing. There are complications with how the API server sees the static pod (because it is notified as well of its creation) versus how the pod is represented within the Kubelet.
How to reproduce it (as minimally and precisely as possible):
Run end-to-end test suite, and there will be various static pods (most for logging and monitoring) that show up in tracing backend.
What happened:
Static pods export traces to our tracing backend. While this might be useful in later iterations, we are not interested in these traces in our current version.
What you expected to happen:
I expect these traces to not be exported into out backend.
How to address
There are Kubelet methods that deal with this, and we could hook some logic in here, but it might not be worth doing. There are complications with how the API server sees the static pod (because it is notified as well of its creation) versus how the pod is represented within the Kubelet.
How to reproduce it (as minimally and precisely as possible):
Run end-to-end test suite, and there will be various static pods (most for logging and monitoring) that show up in tracing backend.