-
Notifications
You must be signed in to change notification settings - Fork 124
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
Issue running kminion with TLS enabled #157
Comments
Hello,
|
|
From broker side, where
Upd: The timestamps are different, since pods are restarting in crashloop, so taken some random |
@mrandreyeff I'm sorry, I haven't seen this error before. As you've already figured out this error messages comes from Go. The kafka client we use just uses Go's underlying TLS dialer, so there's not much that we could do about it I think. Maybe you want to submit an issue at the Go repository and see what additional information you could provide there to figure out what's going on? I'm afraid I can't be of help here otherwise. |
@weeco , do you know if someone uses/used TLS with kminion, or if there were successful tests using SSL? |
@mrandreyeff Yes, KMinion as well as Redpanda Console where the same kafka library and bootstrapping code is used against a lot of TLS secured clusters with all kinds of different distributions (Redpanda, Amazon MSK, Apache Kafka, Confluent Cloud, ...) |
Thanks, then it is probably worth to dig deeper and search on my side |
hi, we have some clusters with custom CA. those regressed recently w/ kminion, while older version & kafka-minion work. the ca file is in pem format. we will give some log soon. Sorry to disappoint, our problem is different. To support old kafka-minion in paraller, we set both Since rev a066, {
"level": "fatal",
"ts": 1658812168.1207764,
"caller": "kminion/main.go:43",
"msg": "failed to parse config",
"error": "1 error(s) decoding:\n\n* 'kafka.tls.ca[0]' expected type 'uint8', got unconvertible type 'map[string]interface {}', value: 'map[file:map[path:kafka_chain.pem]]'",
"stacktrace": "main.main\n\t/home/hdhoang/github/kminion/main.go:43\nruntime.main\n\t/usr/lib/golang/src/runtime/proc.go:250"
} in our case, kminion hasn't reached network conn stage yet. Sorry for mixing things up, we'll work around this locally. |
Hi there,
I'm trying to enable TLS, so I've added TLS files and configs:
After applied, I get error:
There are multiple other clients using java and python, also tried the same TLS credentials with python (PEM format) - worked well. Kafka brokers use Java 11, so according to docs it shall be TLS 1.3.
As far as I see, after some googling shows the error shall come from https://github.com/golang/go/blob/master/src/crypto/tls/handshake_client_tls13.go#L296
Tried also with TLS 1.2 and 1.3 via openssl client - works well:
Does anybody use TLS 1.3 with kminion (or underlying go Dial library)?
Are there any configs that may help from broker/client side?
The text was updated successfully, but these errors were encountered: