To support the metrics stack (and the debugger), we need the kar sidecar to listen on :runtimePort (not 127.0.0.1:runtimePort) when we know we are running on Kubernetes, even if we are running both kar and the application in a single container and thus the application could talk to kar using just localhost:3500.
To support the metrics stack (and the debugger), we need the kar sidecar to listen on :runtimePort (not 127.0.0.1:runtimePort) when we know we are running on Kubernetes, even if we are running both kar and the application in a single container and thus the application could talk to kar using just localhost:3500.