Release 1.2.0 of the provider which included support for IAM role chaining has a bug that keeps it from operating. This is due to the change added to read kc.TLS.DialTimeoutSeconds. This requires TLS config in the secret, which creates a conflict as it causes the provider to set two configes cannot create new Kafka client: cannot set both Dialer and DialTLSConfig.
We need to delete the opts = append(opts, kgo.Dialer((&tls.Dialer{NetDialer: &net.Dialer{Timeout: time.Duration(kc.TLS.DialTimeoutSeconds) * time.Second}}).DialContext)) in the aws-msk-iam since that is dealt with (msk requires tls) with
} else if isAwsMskIam {
// AWS-MSK-IAM requires TLS; enable with default config
opts = append(opts, kgo.DialTLS())
}
/cc @fernandezcuesta
Release 1.2.0 of the provider which included support for IAM role chaining has a bug that keeps it from operating. This is due to the change added to read
kc.TLS.DialTimeoutSeconds. This requiresTLSconfig in the secret, which creates a conflict as it causes the provider to set two configescannot create new Kafka client: cannot set both Dialer and DialTLSConfig.We need to delete the
opts = append(opts, kgo.Dialer((&tls.Dialer{NetDialer: &net.Dialer{Timeout: time.Duration(kc.TLS.DialTimeoutSeconds) * time.Second}}).DialContext))in theaws-msk-iamsince that is dealt with (msk requires tls) with/cc @fernandezcuesta