Piotr Wielgołaski

with recent changes making use of eks:DescribeNodegroup https://github.com/kubernetes/autoscaler/commit/b4cadfb4e25b6660c41dbe2b73e66e9a2f3a2cc9 can we use health information from nodegroup https://docs.aws.amazon.com/cli/latest/reference/eks/describe-nodegroup.html Unhealthly node group should be excluded from calculation

it should help also for https://github.com/Kong/kubernetes-ingress-controller/issues/5175

It looks that this is underlying issue https://stackoverflow.com/questions/28568188/java-net-uri-get-host-with-underscores

I would love ingress format, but it could be problematic if different filtered are used. Version relying on index of first route sound risky, as adding new route could change...

Also it would be very useful to know k8s service and namespace in access log

this looks like to be fixed on main branch, so can you close it?

I build custom release locally, but it does not work out of box, so anyway some adjustment need to be done to make it work before release

@skagedal my scenario was simple, use docker context to connect with remote docker instance. when I rebuild latest code I wanted to give a try, but it don't work. it...

I take another swing on this and simple change in EnvironmentAndSystemPropertyClientProviderStrategy https://github.com/piotrwielgolaski-tomtom/testcontainers-java/blob/de1324ed2800eff4da326d0c23d281399d006bc0/core/src/main/java/org/testcontainers/dockerclient/EnvironmentAndSystemPropertyClientProviderStrategy.java#L51 ``` case "autoIgnoringUserProperties": dockerClientConfig = configBuilder.build(); applicable = dockerClientConfig.getDockerHost() != null; break; ``` make it work a bit...

@skagedal The best that I can find https://github.com/docker/cli/blob/a0756c3c2cacebf5e5dc6454cc280c3ddf675176/docs/reference/commandline/context_inspect.md?plain=1#L42 I thin that this path if exist should be used for SSL config, of course if skip is not true.