Strimzi
Replies: 2 comments 5 replies
-
|
It has been working fine in the past by the same configuration, when I redeployment today, it doesn't work.... |
Beta Was this translation helpful? Give feedback.
-
|
I‘m try to install the latest of strimzi, it output below info: io.strimzi.operator.common.operator.resource.TimeoutException: Exceeded timeout of 300000ms while waiting for Ingress resource qa-broker-kafka-bootstrap in namespace kafka to be addressable │
│ at io.strimzi.operator.common.VertxUtil$1.lambda$handle$1(VertxUtil.java:154) ~[io.strimzi.operator-common-0.37.0.jar:0.37.0] │
│ at io.vertx.core.impl.future.FutureImpl$3.onFailure(FutureImpl.java:153) ~[io.vertx.vertx-core-4.4.4.jar:4.4.4] │
│ at io.vertx.core.impl.future.FutureBase.lambda$emitFailure$1(FutureBase.java:69) ~[io.vertx.vertx-core-4.4.4.jar:4.4.4] │
│ at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174) ~[io.netty.netty-common-4.1.94.Final.jar:4.1.94.Final] │
│ at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167) ~[io.netty.netty-common-4.1.94.Final.jar:4.1.94.Final] │
│ at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) ~[io.netty.netty-common-4.1.94.Final.jar:4.1.94.Final] │
│ at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569) ~[io.netty.netty-transport-4.1.94.Final.jar:4.1.94.Final] │
│ at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[io.netty.netty-common-4.1.94.Final.jar:4.1.94.Final] │
│ at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[io.netty.netty-common-4.1.94.Final.jar:4.1.94.Final] │
│ at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[io.netty.netty-common-4.1.94.Final.jar:4.1.94.Final] │
│ at java.lang.Thread.run(Thread.java:833) ~[?:?] |
Beta Was this translation helpful? Give feedback.
-
|
The errors from the first log are completely unrelated to the Kafka cluster deployment. They just suggest you are trying to rebalance the cluster without the deployment being complete / Cruise Control being enabled. This error is a bit more useful. It suggests that your Ingress controller did not accepted the Ingress resources and updated their status with an address. That could mean you are using an incompatible Ingress controller or have it somehow misconfigured. Possibly it could also mean you are missing the right Ingress class etc. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot for your quick support! strange, I'm not modify any configuration for k8s, It works fine in the past. someone created new one instance of kafka, It doesn't work. default IngressClass bellow, ❯ kubectl get IngressClass -o yaml
apiVersion: v1
items:
- apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata:
annotations:
ingressclass.kubernetes.io/is-default-class: "true"
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"networking.k8s.io/v1","kind":"IngressClass","metadata":{"annotations":{"ingressclass.kubernetes.io/is-default-class":"true"},"name":"nginx"},"spec":{"controller":"k8s.io/ingress-nginx"}}
creationTimestamp: "2023-09-05T03:18:38Z"
generation: 1
name: nginx
resourceVersion: "1019025"
uid: 9f00e0ff-0516-4e0f-9916-98ea0312ec8c
spec:
controller: k8s.io/ingress-nginx
kind: List
metadata:
resourceVersion: ""Ingress args: containers:
- name: controller
image: >-
registry.k8s.io/ingress-nginx/controller:v1.5.1@sha256:4ba73c697770664c1e00e9f968de14e08f606ff961c76e5d7033a4a9c593c629
args:
- /nginx-ingress-controller
- '--publish-service=$(POD_NAMESPACE)/ingress-nginx-controller'
- '--tcp-services-configmap=$(POD_NAMESPACE)/tcp-services'
- '--udp-services-configmap=$(POD_NAMESPACE)/udp-services'
- '--election-id=ingress-controller-leader'
- '--controller-class=k8s.io/ingress-nginx'
- '--ingress-class=nginx'
- '--configmap=$(POD_NAMESPACE)/ingress-nginx-controller'
- '--validating-webhook=:8443'
- '--validating-webhook-certificate=/usr/local/certificates/cert'
- '--validating-webhook-key=/usr/local/certificates/key'
- '--watch-ingress-without-class=true'
- '--enable-ssl-passthrough'
- '--default-ssl-certificate=ingress-nginx/gtlconlycert' |
Beta Was this translation helpful? Give feedback.
-
|
Could it be caused by this parameter?
|
Beta Was this translation helpful? Give feedback.
-
|
Possibly, I guess. That might be more question for the Ingress folks about what exactly it does. |
Beta Was this translation helpful? Give feedback.
-
|
Hello Jakub, It works, but I didn't know why. I just drop the so strange |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Bug Description
I try to delete the
kafkanamespace, and I redeployed strimzi-0.32.0 cluster operator, and then create a new instance of kafka cluster. finally I sew the logs of strimzi-cluster-operator-f696c85f7-blmlj podlogs details:
Steps to reproduce
Expected behavior
No response
Strimzi version
0.32.0
Kubernetes version
Kubernetes 1.24.14
Installation method
yaml
Infrastructure
SAP-Gardener
Configuration files and logs
the
ssl-passthroughoption is enabled of ingress-v1.5.1Additional context
Beta Was this translation helpful? Give feedback.
All reactions