I see there is a DestinationRule - specific config in regards to the tcp keepAlive setting.

I have deployed my app broken down in several microservices in an istio- based k8s infrastructure.

Since in my DestinationRule I have not set up any of the above configs, my question is how will the tcp keepAlive behaviour be laid out at the end of the day?

Will there be no keepAlive functionality?

Will (any) main-container keepAlive workings be able to perform end-to-end over all the connection path and actually enforce the keepAlive in tcp level somehow?

edit: Perhaps I misinterpreting the docs, but what I get from the attached screenshot, is that in the absence of ConnectionPoolSettings.TCPSettings, the keepAlive functionality is not set.