kostas-meladakis commented on issue #691:
URL: 
https://github.com/apache/openwhisk-deploy-kube/issues/691#issuecomment-1117177389

   > I have been successfully able to deploy this project with kind and trigger 
actions. My goal was to get a kafka feed setup to trigger an action via a rule 
but no matter what I do it seems like my kafka feed does not pick up the 
messages. It appears as if it successfully creates the trigger and a response 
is recevied it looks like from the logs but messages don't propagate. Is it 
possible I am missing stuff from here : 
https://github.com/apache/openwhisk-package-kafka
   
   ### Try do the following:
   
   - Follow generic kafka, it is simpler
   - If create successful trigger  then go to section, produce _generic kafka 
event_ 
   There is this command: **wsk_ action invoke /messaging/kafkaProduce -p 
brokers "[\"mykafkahost:9092\", \"mykafkahost:9093\"]" -p topic mytopic -p 
value "This is the content of my message"**
   It is missing the correct path (actually is 
/whisk.system/messaging/kafkaProduce). Also by default in your deployment there 
is only one broker at 9092. To find the write port you have to check the 
interal IP of kafka image (for me was 10.1.0.182:9092)
   So your command to create and invoke should be: 
   `wsk trigger create MyKafkaTrigger0 -f /whisk.system/messaging/kafkaFeed -p 
brokers "[\"10.1.0.182:9092\"]" -p topic mytopic -p isJSONData true`
   and
   `wsk action invoke whisk.system/messaging/kafkaProduce -p brokers 
"[\"10.1.0.182:9092\"]" -p topic mytopic -p value "This is the content of my 
message" --blocking`
   _where 10.1.0.182 is the ip of the already deployed kafka pod_
   - If the above fail, consider invoke the trigger via npm library, it is 
built in and easy to use, check here  
[](https://github.com/apache/openwhisk-client-js#fire-trigger)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to