Andrew Pruski has a guide for us:
A while back I wrote about how to use a Cross Platform (or Clusterless) Availability Group to seed a database from a Windows SQL instance into a pod in Kubernetes.
I was talking with a colleague last week and they asked, “What if the existing Windows instance is already in an Availability Group?”
This is a fair question, as it’s fairly rare (in my experience) to run a standalone SQL instance in production…most instances are in some form of HA setup, be it a Failover Cluster Instance or an Availability Group.
Read on for the tutorial. There are quite a few steps involved.