Strimzi
Replies: 9 comments 28 replies
-
|
You should probably start by sharing the full logs from the operator as well as from the Connect pod. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Operator logs:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I tried another connect with annotation removed. Connect starts but when I add a connector, get below error in operator: |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Well, if you disable the connector operator, you cannot add connectors using the KafkaConnector resources. You have to use the Connect REST API directly. |
Beta Was this translation helpful? Give feedback.
-
|
Kafka connect logs: |
Beta Was this translation helpful? Give feedback.
11 replies
-
|
not sure, but we've experimentally determined that it echoes the addition of https://repo1.maven.org/maven2/io/debezium/debezium-connector-postgres/3.0.0.Final/debezium-connector-postgres-3.0.0.Final-plugin.zip |
Beta Was this translation helpful? Give feedback.
-
|
I don't think that is about tracing but about metrics. That is why it says |
Beta Was this translation helpful? Give feedback.
-
|
done. but the same result: |
Beta Was this translation helpful? Give feedback.
-
|
That is not a Java system property. You would need to set it in system properties. Not in |
Beta Was this translation helpful? Give feedback.
-
that fixed the problem |
Beta Was this translation helpful? Give feedback.
-
|
This is the generated networkpolicy: |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Correct. The question is why does it seem to not do what it is expected to do => allow the access. |
Beta Was this translation helpful? Give feedback.
-
|
Generated operator pod description: |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
That seems to have the label, so that looks good 🤷 |
Beta Was this translation helpful? Give feedback.
-
|
fyi, with a previous version (0.31.1), I had deployed the connect without annotation and the connector with the label. It worked. However, after upgrading to latest version, it does not work |
Beta Was this translation helpful? Give feedback.
-
|
In the redis example above, I dont have the annotation in the connect resource, but the connector now gives the missing annotation error |
Beta Was this translation helpful? Give feedback.
-
|
There were no changes around this in recent Strimzi versions. The annotation has always been required to use the KafkaConnector resources. And the network policy also looks the same for a long time. |
Beta Was this translation helpful? Give feedback.
-
|
In all the examples, I see the annotation is commented by default. |
Beta Was this translation helpful? Give feedback.
-
Okay, this was a mis-statement. As I had multiple connectors, some with annotation and some without, I got confused. So, it did work earlier with annotation only. So, I still am trying to investigate regarding the network policy as that seems to be the probable cause. |
Beta Was this translation helpful? Give feedback.
9 replies
-
|
Is there a way to prevent the creation of the network policy? I want to test whether the connector comes up without the network policy. Since, the operator automatically regenerates the network policy after manual deletion, I cannot test it |
Beta Was this translation helpful? Give feedback.
-
|
There is an environment variable you can use to tell the operator to not manage any network policies. You would need to check the docs for the exact name as I do not remember it out of my head. But you could try that. |
Beta Was this translation helpful? Give feedback.
-
|
ok. I found that doc. Does it disable all network policies? I was looking only to disable for connect resource only |
Beta Was this translation helpful? Give feedback.
-
|
It applies to all network policies. There is no way to disable them only for Connect. Also, it does not delete the network policies. It leaves them in place as they are when you set the environment variable => you can for example delete or edit them manually. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your prompt responses. |
Beta Was this translation helpful? Give feedback.
-
|
After disabling network policy creation, both the connect and connector resource are starting up. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
sorry for bothering me, Now I have changed the configuration to connect to kafka (it can connect) but when I start configuring bedezium to be able to call postgres, debezium logs say "Producer clientId=vcr-cdc-sandbox] Failed authentication with kafka-03.sbkafka.hehe.vn/172.26.x.x (channelId=-3 ) (SSL handshake failed" Here is my config: I have had this error for 2 3 days today and have not found a solution, can you help me? I thank you. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
That does not look like Strimzi. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am using the Operator to create a Kafka cluster. I created new Kafka connect as below:
The state is never ready:
Why is it calling the `api' endpoint (debezium-connect-api.test.svc.cluster.local) instead of the normal endpoint(debezium-connect.test.svc.cluster.local) ?
If I remove the annotation
strimzi.io/use-connector-resources: "true", then the resource starts successfully.However, when I try to now add KafkaConnector resource, it fails with error that the annotation is missing
Beta Was this translation helpful? Give feedback.
All reactions