Open corey-aloia opened 3 years ago
@corey-aloia, Thanks for bringing this issue to us. It seems that there is an issue on our side where we are not handling the namespaced services. I've opened a bug on our side and will update the thread once it is fixed.
@corey-aloia I'm not able to repro this issue. Can you share the following details:
Apply the following yaml:
Notice that the hostname will be updated to:
my-service.svc.cluster.local
now add the namespace:
And the bridge will not start with
Now try the FQDN
the k8 bridge will start, but now the /etc/hosts will have:
my-service.mynamespace.svc.cluster.local.svc.cluster.local
Here is the log output that occurs when adding the namespace, and getting the
Value cannot be null
error: