Concurrency-Issue/ Event-Loss while deploying CR in Kubernetes Cluster using Helm Chart

[shreegithub]

We have usecases to create Kafka topic on AWS MSK on the fly when any application is deployed within Kubernetes Cluster.

We have written one CR/CRD((Api Group "kafka.abc.com")) having the details of topic information. This CR is deployed as part of the application deployment as Helm Chart.

We have written one hook in operator to listen this CR and do appropriate action to create/update topic based on captured Events(Add/Modify).

When Helm chart deploy multiple CR of same Api Group("kafka.abc.com") then shell-operator is able to capture "Add" Event of only one CR. Other "Add" Events of different CR are being losses because all the CR are added into K8s cluster at same timestamp.

Is there any solution to capture the events which got missed due to concurrency?