You can see here: https://github.com/argoproj/argo-rollouts/issues/132#issuecomment-518519954 an answer by jessesuen: “Aside from the Deployment resource, the only other native k8s resources that might need similar advanced deploy strategies are: StatefulSet and DaemonSet. But both of these resources have very different behaviors that would warrant an entirely new resource kind and controller. I don’t think a generic approach could handle all three types because the manner in which these resources manage their pods are wildly different. So while it’s conceivable that we would introduce something like a StatefulRollout or DaemonRollout in the future, in all likelihood, these other kinds would need very specific/different implementations to mirror their k8s native counterparts. By that same token, it’s hard for me to fathom how the rollout logic could be generalized to CRDs like Knative, FederatedDeployment, because the controller would have no understanding nor the ability to control how these CRDs manage their pods.”