Lightning Talk: Who Are You? Solving the Container ID Resolution With Cgroupv2 - Vincent Boulineau

Don't miss out! Join us at our next Flagship Conference: KubeCon + CloudNativeCon events in Hong Kong, China (June 10-11); Tokyo, Japan (June 16-17); Hyderabad, India (August 6-7); Atlanta, US (November 10-13). Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at https://kubecon.io

Lightning Talk: Who Are You? Solving the Container ID Resolution With Cgroupv2 - Vincent Boulineau, Datadog

In containerized environments, one key challenge of pushing observability data is to identify the sender, to allow data enrichment, i.e. attaching attributes, tags, metadata based on container or Pod metadata.
This problem has been commonly solved by asking the sender to provide its own container id, easily available through /proc/self/cgroup.

When Datadog started evaluating cgroupv2, it quickly became apparent that this approach was not usable anymore, prompting us to find new solutions as the most common workaround (using mountinfo) is actually not reliable.
In this talk we'll explain why the container id is not available anymore (due private cgroup namespace) and present two solutions that we worked on.

We will go through the benefits of each one and will share how these solutions could be used in other observability projects, like OpenTelemetry.