I wish I could provide a more straightforward answer, but the reality is that you have to consider at least three moving parts regarding licensing:
Kafka Connect: This is the runtime part of the architecture and provides a way for connectors to execute. Kafka Connect is part of Apache Kafka, and therefore, it is available under the Apache License 2.0 license. So no charges or fees for it.
Kafka Distribution: Apache Kafka is a piece of software made available over different distributions. A few examples include Confluent, Cloudera, Red Hat, IBM, among others. When you decide to use bits outside the Apache jurisdiction, that is, when you do not obtain the software from kafka.apache.org, you have to be mindful of the distribution’s licensing. Confluent has different distributions, each one with its license. If you, for example, decide to use enterprise distribution, you may need to worry about charges. I would chat with some Confluent folks such as @rmoff for more information about distributions.
Connector: Each connector has its own licensing. Specifically:
confluentinc/kafka-connect-jdbc Confluent Community License
Lastly, be mindful of where you’re getting the software from. This is particularly important if you’re using container images. Not all images are from the same author.