F5 BIG-IP / Container Connector integration with Microsoft Azure Service Fabric?

Are there any planned integrations with F5 Container Connector and Microsoft Azure Service Fabric? We are looking into using Azure Service Fabric as an on-prem PaaS in our private data centers, and are trying to find answers regarding using BIG-IP as the external proxy in front of Service Fabric (LTM + DNS). We can't seem to find any information regarding what the pool memberships would look like, how monitors would be configured, etc...) let alone tightly integrating the BIG-IP with SF using something such as Container Connector as is done with K8S. There seems to be a lack of documentation for how Azure Service Fabric can be deployed as a stand-alone solution offering in a private data center but still work with existing technologies such as BIG-IP for application delivery purposes of the services hosted in it.