Service Fabric on Kubernetes?

Hello,

I am battling with a question that has recently been raised by some third parties we’ve spoken to, and I’d like to get some perspectives.

We develop and run a fairly complex microservices application on Azure Service Fabric using the officially supported deployment options. I completely understand that deploying Service Fabric on Kubernetes is not something that’s supported. That said, given the increasing popularity of Kubernetes, the question has started coming up more often, and I’d like to understand if this has ever been attempted by anyone and, if so, what the outcomes were.

From my understanding, this would essentially mean deploying one orchestrator within another orchestrator. I imagine that a single-node development setup might not be impossible since it’s self-contained within a single "box".

• Has anyone ever attempted running Service Fabric inside Kubernetes (even experimentally - multi-node or single-node)?
• If yes, what were the results or lessons learned? I would appreciate any links to external resources regarding this if you came across such.
• If not, what would you consider to be the main blockers for SF on K8s?

I appreciate this is more of a "curiosity" question than a best-practice one, but it would be really valuable to hear any insights or experiences outside of my own circle of SF focused minds :).

Thank you in advance!