You may to do it with Nutanix Volumes to present shared storage by iSCSI to hyper-v host especially for Windows Failover clustering if it you mean, but why you do not move this workload from hyper-v to AHV? 

We have enough CPU and RAM available at UCS , just lack of storage ,so  using storage only nodes which guest VM cant host.

Yes true, I mean the same I want to create ABS volume and connect to ucs host via iSCSI and present as data store to Hyper-V. But things which confused me is below link . Which says

“ Do not use Volumes to create an iSCSI data-store to Hyper-V or ESXi hosts. This configuration is not supported. “ are they talking about Nutanix based Hypervisor or external ?

I guess it is not supported because Nutanix has an option to deploy a hyper-v based installation of Nutanix HCI, but technically it may work fine

p.s. https://docs.microsoft.com/en-us/windows-server/failover-clustering/clustering-requirements

iSCSI: If you are using iSCSI, each clustered server should have one or more network adapters or HBAs that are dedicated to the cluster storage. The network you use for iSCSI should not be used for network communication. In all clustered servers, the network adapters you use to connect to the iSCSI storage target should be identical, and we recommend that you use Gigabit Ethernet or higher.

Thanks , Yes Technically looks doable, but has anyone tried this ? before we can commit for it ?

Or any near confirmation documents which shows this kind of solution for external Hypervisor.

Or any other supported solution ?

Any views on use SMB , if ISCSI doesn't support.

https://portal.nutanix.com/page/documents/details?targetId=HyperV-Admin-AOS-v5_18:hyp-connection-requirements-outside-cluster-hyperv-r.html

It might be doable but it is certainly not supported.

All options in which we present storage externally to hosts such as ESXi and Hyper-v are usually as temporary options to migrate VMs onto those particular containers but with the end goal of eventually running such VMs in the AOS cluster and not with the goal of presenting those containers as persistent storage for the External hosts.

Having such setups might cause instability in the AOS cluster that is providing the storage to the external hosts.

the following kb has additional information on it, but again, just for migration purposes:

https://portal.nutanix.com/page/documents/kbs/details?targetId=kA0600000008SdpCAE