-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
good first issueUp for grabsUp for grabsscope/backendstatus/acceptedAn issue which has passed triage and has been acceptedAn issue which has passed triage and has been acceptedtype/enhancementEn enhancement to an already existing featureEn enhancement to an already existing feature
Milestone
Description
Which version of the app are you running?
Tag: v0.4.0 and master@d9e74deb287e7b81172c6988dd0f99b1a97d9036
Is your proposal related to a problem?
Currently it's not possible to configure a Kafka Connect component that has TLS Client Auth required but there could be also other settings that need to be passed to the Kafka Connect Client.
Describe the solution you'd like
I would like to propose adding a Properties field to the model.KafkaConnectCluster class like the model.KafkaCluster and use the properties in the client instantiation.
Therefore the Kafka Connect component could be configured in the following way to allow TLS Client Auth:
KAFKA_CLUSTERS_0_KAFKACONNECT_0_PROPERTIES_SECURITY_PROTOCOL=SSL
KAFKA_CLUSTERS_0_KAFKACONNECT_0_PROPERTIES_SSL_TRUSTSTORE_LOCATION=ca.jks
KAFKA_CLUSTERS_0_KAFKACONNECT_0_PROPERTIES_SSL_TRUSTSTORE_PASSWORD=xxxx
KAFKA_CLUSTERS_0_KAFKACONNECT_0_PROPERTIES_SSL_KEYSTORE_LOCATION=foobar.jks
KAFKA_CLUSTERS_0_KAFKACONNECT_0_PROPERTIES_SSL_KEYSTORE_PASSWORD=xxxx
Describe alternatives you've considered
N/A
Additional context
This issue is propably related to #930.
If I get some spare time, I will have a look by myself at it and create a PR.
whatsupbros
Metadata
Metadata
Assignees
Labels
good first issueUp for grabsUp for grabsscope/backendstatus/acceptedAn issue which has passed triage and has been acceptedAn issue which has passed triage and has been acceptedtype/enhancementEn enhancement to an already existing featureEn enhancement to an already existing feature