Open
Description
Right now, Create is special because it fails when objects it tries to create are discovered as already existing during the call of the create{Object} (i.e. StatefulSet, Service, etc.). Subsequently, the next sync will find the cluster in a half-created state and sync all definitions from the cluster manifest with the actual state of the Kubernetes. This actually results in Create being equivalent to a Sync at the end of the day, but introduces a delay of one one ResyncPeriod before such a cluster can be used.
Given that, I don't see any strong reasons for not replacing Create with Sync altogether for the cluster. In fact, we already run sync every time for the secrets and user roles in the DB, not failing when those already exist.