Strimzi
Replies: 8 comments 21 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.
5 replies
-
This seems strange as your KafkaConnect does not seem to have tracing enabled and that is the only thing Strimzi uses OpenTelemetry for. These errors seem to suggest it has issues with creating / using some of the topcis: Not sure if this is just a temporary issue or not. The log does not seem to contain the time of the operator error. So it is hard to say if it reached the Connect server or not. It could be something in the COnnect cluster or it could be just some networking issue for example. The fact that it talks to the |
Beta Was this translation helpful? Give feedback.
-
|
I checked from operator shell, |
Beta Was this translation helpful? Give feedback.
-
|
That could indicate some issues with network policies? |
Beta Was this translation helpful? Give feedback.
-
|
As when you enable the connector operator, the operator creates a network policy that should make sure you can talk with the Connect API. So I wonder if you are having some wrong labels somewhere or something. |
Beta Was this translation helpful? Give feedback.
-
|
In particular, this label is important on the Cluster Operator: https://github.com/strimzi/strimzi-kafka-operator/blob/main/install/cluster-operator/060-Deployment-strimzi-cluster-operator.yaml#L17 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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