replace etcd with k8s apiserver backed by etcd

[hunchback]

would it be possible to replace etcd with the k8s etcd (which is accessed via the apiserver)?

could we use k8s CRDs to define the captures (and other etcd backed resources)?

would this provide benefits in the multi-cluster use case?