Replies: 1 comment 2 replies
-
What does the full log say? What do your Kubernetes logs say? Could it be some rate limiting or something? You might also consider upgrading to newer Strimzi version as the config provider included there has improved logging: strimzi/kafka-kubernetes-config-provider#24 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Problem:
The
secrets
provider in some KafkaConnectors started to fail to access/resolve the secret values.Worth Noting
secrets
provider had been functioning properly until recently.Detailed Steps:
KafkaConnect
with thesecrets
providerKafkaConnector
with thesecrets
provider to configure the database password from a k8s secretKafkaConnector
is created but the secret value is not resolved.However, the secret does exist in the namespace.
get
access to all secrets in the namespace and there's a role biding for that SA.Question:
Can someone think of reason why this started to happen suddenly and why this can happen to some connectors only?
Environment:
Kafka: quay.io/strimzi/kafka:0.36.0-kafka-3.5.0
Beta Was this translation helpful? Give feedback.
All reactions