Anand Swaminathan

We were able to get this work. We changed the https://github.com/strimzi/strimzi-kafka-operator/blob/main/docker-images/kafka-based/kafka/scripts/kafka_connect_config_generator.sh to support AWS IAM. Also this blog post is super useful as we use Connect with Debezium - https://thedataguy.in/debezium-with-aws-msk-iam-authentication/...

I had to add a bunch of values. The list is available in this blog- https://thedataguy.in/debezium-with-aws-msk-iam-authentication/ Yes, after that build the image for the Kafka Connect, so that Connect can...

Was the job manager having issues ? Did you check logs in the Jobmanager ? ```2019-09-25 19:49:29,474 WARN akka.remote.ReliableDeliverySupervisor - Association with remote system [akka.tcp://flink@wordcount-operator-example-8e8ca53d:6123] has failed, address is now...

I am not aware of something that is available (or straightforward) to achieve this. We have wanted to build some functionality like this in the Operator, we are yet to...

@JRemitz Sounds good. I guess there is one scenario, the deployment object created by the operator will need min/max. no ?

Check this PR for reference: https://github.com/lyft/flinkk8soperator/pull/233/files https://github.com/lyft/flinkk8soperator/blob/master/deploy/crd.yaml

I believe we looked into this. There were several simpler options. Will need to dig a bit.

@JayGhiya Can you share or add relevant links as well? Let me take a look

@maghamravi can you merge? @skidder Can you approve CLA check?

@rmuthupandian Why do you want the ports to be exposed in the Jobmanager service ? From what I understand, prometheus should be able to scrape metrics directly from the Kubernetes...