-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS support for bootstrap server configuration #41
Comments
TLS support is already available. |
you would include something like:
|
Hi Vijit,
Thanks a lot for response.
Do we have option to override “akka” configuration in helm chart, I have not seen this.
If you can share the helm chart actual configuration that will help a lot.
Regards,
Anup
From: Vijit Singhal ***@***.***>
Date: Monday, April 25, 2022 at 8:55 AM
To: SumoLogic/sumologic-kafka-push ***@***.***>
Cc: Anup Kumar Shrivastava ***@***.***>, Author ***@***.***>
Subject: Re: [SumoLogic/sumologic-kafka-push] TLS support for bootstrap server configuration (Issue #41)
you would include something like:
akka: {
kafka.consumer: {
security.protocol: SSL
ssl.truststore.location: /opt/kafka/config/kafka.truststore.jks
ssl.truststore.password: trustore_password
ssl.keystore.location: /opt/kafka/config/client.keystore.jks
ssl.keystore.password: keystore_password
ssl.key.password: key_password
ssl.enabled.protocols: TLSv1.2,TLSv1.1,TLSv1
ssl.client.auth: required
}
}
—
Reply to this email directly, view it on GitHub<#41 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABG2JZYDJHNGOZF43NFFECDVG257RANCNFSM5TPCEZDA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
you can take a look at: https://github.com/SumoLogic/sumologic-kafka-push/blob/main/helm/README.md#configuration Basically, the additional conf needs to be put in a file and that file will be specified at |
Thanks a lot Vijit,
I will work on it and will update on this thread for sure.
Regards,
Anup
From: Vijit Singhal ***@***.***>
Date: Monday, April 25, 2022 at 9:31 AM
To: SumoLogic/sumologic-kafka-push ***@***.***>
Cc: Anup Kumar Shrivastava ***@***.***>, Author ***@***.***>
Subject: Re: [SumoLogic/sumologic-kafka-push] TLS support for bootstrap server configuration (Issue #41)
you can take a look at: https://github.com/SumoLogic/sumologic-kafka-push/blob/main/helm/README.md#configuration
Basically, the additional conf needs to be put in a file and that file will be specified at endpointsSecret parameter in the helm chart.
—
Reply to this email directly, view it on GitHub<#41 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABG2JZ5ZRE5L5KALKBBWB4LVG3CEZANCNFSM5TPCEZDA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@vsinghal13 I have added following configuration Below are the values that we are adding to override values file. extraVolumes: extraVolumes & extraVolumeMounts are being used to add Kafka TLS certificate file. And endpointsSecret, i am having below configuration and kept in one file i.e. "akka.conf" but that is created as secret since endpointSecret are being used as a secret in your helm chart. akka: { While deploying this changes, I am getting below logs, & I think connection has not been made to kafka cluster & still having issues. 2022-04-27 00:51:28 WARN [default-dispatcher-21] o.a.k.c.NetworkClient - [Consumer clientId=consumer-kafka-push-logs-1, groupId=kafka-push-logs] Bootstrap broker 10.220.5.92:9093 (id: -4 rack: null) disconnected Could you please verify and let me know if I am missing any thing here or need some enhancement. |
were you able to run |
Yes |
On pod startup you should see in the logs the kafka consumer configuration. Does it match with what you are setting in the endpointsSecret? The secret should also be formatted as follows: { |
@ddaughertysl Here is my finding This is the actual secret file configuration External Secret is getting created with this name akka-conf But still getting this from pod logs 2022-04-27 16:25:09 INFO [default-dispatcher-10] o.a.k.c.c.ConsumerConfig - ConsumerConfig values: 2022-04-27 16:25:10 INFO [default-dispatcher-10] o.a.k.c.u.AppInfoParser - Kafka version: 2.7.0 As per log, it seems value is not being override.. |
Please have a look at #45 |
@vsinghal13 Have applied the same configuration as what you have mentioned in your PR. But still the SSL configuration dont works in our environment. We have other applications as well on our cluster which uses the same SSL configuration and it does work on them. Also did performed the troubleshooting steps as well and all looks correct from that front. So can you please advise as what might be going wrong ? Logs: 2022-06-24 11:28:35 WARN [default-dispatcher-10] o.a.k.c.c.ConsumerConfig - The configuration 'ssl.client.auth' was supplied but isn't a known config. |
@ddaughertysl any suggestions on this? |
i think this shows progress in that the ssl settings are now being applied and the security protocol is SSL. The question is why aren't they working. Which is a bit harder for us to answer without comparing both the settings that work in your other applications and the sumo-push settings. Also i notice that your ssl.protocol is set to TLSv1.3 and ssl.enabled.protocols don't include that value. So you might also try including v1.3 in the list of enabled protocols. |
@ddaughertysl Did the requested change but still the issue persist. 2022-07-01 09:27:03 INFO [.default-dispatcher-3] a.e.s.Slf4jLogger - Slf4jLogger started 2022-07-01 09:27:05 WARN [default-dispatcher-10] o.a.k.c.c.ConsumerConfig - The configuration 'ssl.client.auth' was supplied but isn't a known config. |
Please send the broker logs since they might have more information about what is happening. Also noticing that you are using the same file for both keystore and truststore. Is that intentional? Can you also send us the settings you are using in your working applications with the passwords redacted? |
The sasl.jaas.config line in the config also looks a little strange. Can you escape the quotes in that config so it looks like the following:
|
Thanks @ddaughertysl for the hint. We have corrected jaas config now. But the tool is failing now with SASL client authenticator error. Several articles online suggests that it is a temporary error which should get resolved once we restart the app. But that is not happening in our case. 2022-07-06 13:28:34 WARN [default-dispatcher-20] o.a.k.c.NetworkClient - [Consumer clientId=consumer-kafka-push-logs-1, groupId=kafka-push-logs] Bootstrap broker xxxxx:9093 (id: -4 rack: null) disconnected Can you please advise, as what can be an issue now ? |
have you configured your |
@ddaughertysl thanks again. it has worked now. But log parsing is failing now with below error. Do we need to configure serdeClass ? Error Logs: 2022-07-06 18:19:16 ERROR [default-dispatcher-28] c.s.s.a.LogProcessor$ - unable to parse log message payload: Jul 01 13:42:06 8f844057-a8f5-4f0d-9b66-3347d9815750 [2022-07-01 13:42:06,957] INFO [SocketServer listenerType=ZK_BROKER, nodeId=2] Failed authentication with /10.x.x.8 (Unexpected Kafka request of type METADATA during SASL handshake.) (org.apache.kafka.common.network.Selector) |
Yes you should be using the JsonLogEventSerde but it also looks like your messages aren't in Json format. Can you fix that? |
@ddaughertysl Logs are in text/string format. Do we need to compulsory move them to JSON format ? |
Yes per the docs https://github.com/SumoLogic/sumologic-kafka-push#supported-message-formats we only support json format at this time. |
Yes. I had to adjust resource configuration.
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Vijit Singhal ***@***.***>
Sent: Tuesday, April 26, 2022 6:16 PM
To: SumoLogic/sumologic-kafka-push ***@***.***>
Cc: Anup Kumar Shrivastava ***@***.***>; Author ***@***.***>
Subject: Re: [SumoLogic/sumologic-kafka-push] TLS support for bootstrap server configuration (Issue #41)
were you able to run helm upgrade successfully after the changes that you made?
—
Reply to this email directly, view it on GitHub<#41 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABG2JZ4KTZE5VTAI2GFX7PDVHCIP7ANCNFSM5TPCEZDA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Currently it seems there is support to use TLS for bootstrapServers. We have Kafka brokers where TLS and authentication enabled to connect the broker server.
Can we have this support, so that we can use this helm chart to publish Kafka logs on Sumologic.
The text was updated successfully, but these errors were encountered: