Current situation

Today, when starting IG in Kubernetes, the socket path is determined by an environment variables or falls back to a default based on the container runtime detected.

Impact

The socket path needs to be pre-determined as part of the IG installation.

Ideal future situation

In Kubernetes, retrieve the socket path from the node.

Implementation options

In Kubernetes, we can query the API server to retrieve the kubelet configuration, which includes the container runtime endpoint