Kubernetes Service not created about kubedock HOT 6 CLOSED

Ah, now I see what has been missing on my side. Setting .withNetworkAliases("foo") on the Testcontainer only is not enough. I also need to set .withNetwork(Network.newNetwork()) and I was missing this before.

With that in place I do actually see the Kubernetes Service being created properly. Thank you, that works for me! Sorry for the noise!

from kubedock.

I removed it here: 625b4ab because I thought it was not used. :-/

from kubedock.

Reverted the change, can you confirm this is what you expected?

from kubedock.

I am not tied to the kd-* service name but I'd expect that a Service resource is being created when there is an exposed port on the container. I also see that this is currently not working with a NetworkAlias set on the Testcontainers container.

from kubedock.

How are you using/determining which service to use? The network alias services (named according to that alias) didn't change. Another change that might have impacted you is that kubedock not creates deployments anymore, but pods directly.

from kubedock.

No worries, thanks for reporting. I will leave the default generated service in. I removed the kd- default service again.

from kubedock.