Track ACK resources without depending only on final status

[nromriell]

Is your feature request related to a problem? Related to https://github.com/aws-controllers-k8s/community/issues/2062 The problem is that if the controller receives any interrupt between the initial create api call and the resource update the result is duplicate resources being created

Describe the solution you'd like Controller protects against duplicate resources by tracking reconcile state before API call and as part of the remote resource

Describe alternatives you've considered Initial idea is to:

• update the resource status to mark it as pending before calling the create call
• use a unique tag based on the uid of the crd resource (or a generated unique id) to tag the remote resource for tracking as part of the initial create
• if on reconcile a controller finds a pending status it will first attempt to reconcile the remote object with the unique tag before running the create again

@a-hilaly has brought up some good initial points to investigate:

• What's the general support for finding resources by tag with the AWS API?
• What about services that do not support list API calls?

The purpose of this is feature request is to start a discussion on this issue, gather additional ideas for resource tracking, and track investigation of the initial concept

We can also continue discussion in the slack thread

[nromriell]

@a-hilaly has suggested that instead use defer/recover handling to recover and still write out to the kubernetes object even when an error occurs which seems like a good way to handle these situations more universally