client-python VS kubebuilder-declarative-pattern

I am using the kubernetes python client. In the event that kubernetes isn't available when my code starts up, I would like to retry the connection.

Hi, first time raising a post here. What are your thoughts on kubebuilder-declarative-pattern? My team and I has been working on our first k8s operator with operator-sdk for a while now, though it's only at the level of installation atm. Despite that, we found writing the simpliest Reconcilation logic of applying YAML idempotently to be complex enough and quite error-prone. (e.g. exposing a property to override `Service` resources name requires additional controller-logic to check if there's a service account of different name created previously and prune it to prevent dangling) . This is where I stumble across kubebuilder-declarative-pattern plugin, which has many nice features (e.g. apply --prune --applyset to address issue above), declarative-YAML and Reconcile logic out of the box.