Avoiding state is theoretically a nice goal. But a generic “none” backend as described in the OP would simply be impossible. The support for diffing desired vs

Avoiding state is theoretically a nice goal. But a generic “none” backend as described in the OP would simply be impossible. The support for diffing desired vs actual state must be implemented in the resource provider, which in turn need to be supported by the cloud API. Ubiquitous labels, namespaces and global query performance seem to be the primary blockers today, judging by most other comments here. Interesting thought if someone would attempt to make such a provider. Also interesting to look at existing providers if they avoid state internally when possible or just use it because it is available. Looking at the challenges with kubectl apply --purge, already having all enablers laid out, it would require big effort.