You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are currently experiencing a problem between ArgoCD and Strimzi operator. We are deploying topics and kafka connectors via the operator's CRDs.
We have a use case that requires us to delete the application and recreate it in order to validate the production and consumption of messages to and from our kafka topics.
When we delete the application via the Argocd UI, the application is immediately recreated (autoSync, by design), the topics are created and then the connectors too.
However, at random, it seems that the creation delay between a topic named A and its connector named B is too fast, so that the connector task is not launched because the topic is not really ready. Is there a way in ArgoCD or in strimzi to check that a resource is ready before creating the one that depends on it? I've tested Hooks, but they don't correct the problem. I don't know if it's a strimzi bug or not.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
we are currently experiencing a problem between ArgoCD and Strimzi operator. We are deploying topics and kafka connectors via the operator's CRDs.
We have a use case that requires us to delete the application and recreate it in order to validate the production and consumption of messages to and from our kafka topics.
When we delete the application via the Argocd UI, the application is immediately recreated (autoSync, by design), the topics are created and then the connectors too.
However, at random, it seems that the creation delay between a topic named A and its connector named B is too fast, so that the connector task is not launched because the topic is not really ready. Is there a way in ArgoCD or in strimzi to check that a resource is ready before creating the one that depends on it? I've tested Hooks, but they don't correct the problem. I don't know if it's a strimzi bug or not.
Beta Was this translation helpful? Give feedback.
All reactions