|
|
|
|
|
|
by andrewmackrodt
1120 days ago
|
|
|
While this may not solve your problem, I use docker-network-connect which lets me connect directly to containers running in the 172.x.x.x range. By default, macOS does not support routing from host to containers by IP https://github.com/chipmk/docker-mac-net-connect. In the kubernetes case (I am using k3d on my Mac) pods aren't directly routable but with metallb, load balancer IP addresses can be connected to directly and there's no worry about port conflicts as there might be with k3d's default servicelb implementation (this is my bootstrap script https://github.com/andrewmackrodt/k3d-boot). If you need to connect to specific pods directly and it doesn't make sense to change your pod config, kubectl port-forward may suffice? |
|
|