Support for emitting kubernetes events

[a-hilaly]

Currently, ACK controllers don't emit Kubernetes events during AWS resource lifecycle operations. Users must rely on examining resource status conditions or controller logs to understand the state of their resources and troubleshoot issues. this lack of event emission limits observability and prevents integration with some other Kubernetes event based monitoring and alerting systems

ACK should emit Kubernetes events for significant resource lifecycle operations including:

• resource creation (e.g initiated, in progress, AVAILABLE)
• resource ready/available state transitions
• update operations (initiated, completed)
• deletion operations (initiated, completed)
• API errors (throttling, permissions, validation)
• state transitions (e.g with an RDS instance: creating->backing-up->available)

This would enable users to use kubectl describe and kubectl get events to track ACK operations, integrate with existing k8s monitoring stacks (prometheus/alertManager via kube-state-metrics, datadog...)

Checkout this video https://www.youtube.com/watch?v=GBxfAQnHHbE
Event API docs: https://kubernetes.io/docs/reference/kubernetes-api/cluster-resources/event-v1/

[knottnt]

Would any of these proposed events have relationships to the existing ACK status conditions?