Commits on Jun 3, 2024

1. Kubeconfig exec authentication when connecting with --docker from a WSL …

   Clusters like Amazon EKS often use a special authentication binary that
   is declared in the kubeconfig using an `exec` authentication strategy.
   This binary is normally not available inside a container. Consequently,
   a modified kubeconfig is used when `telepresence connect --docker`
   executes, appointing a `kubeauth` binary which instead retrieves the
   authentication from a port on the Docker host that communicates with
   another process outside of Docker. This process then executes the
   original `exec` command to retrieve the necessary credentials.
   
   This setup was problematic when using WSL, because even though
   `telepresence connect --docker` was executed on a Linux host, the Docker
   host available from `host.docker.internal` that the `kubeauth` connected
   to was the Windows host running Docker Desktop. The fix for this was to
   use the local IP of the default route instead of `host.docker.internal`
   when running under WSL.
   
   Signed-off-by: Thomas Hallgren <[email protected]>

   

   thallgren committed Jun 3, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 54233bc
   • Browse repository at this point

   Copy the full SHA

   54233bc View commit details

   Browse the repository at this point in the history