Replies: 1 comment · 9 replies
-
I guess sharing logs from the Cluster Opertor or the full resource including the status might show what the issue it. But the compatibility between different Ingress controllers is not good. So it is quite likely it will be caused by that. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Now I try with LB option and restart operator
Operator log after restart
|
Beta Was this translation helpful? Give feedback.
All reactions
-
it works after restart cluster operator for load balance option. I will go with this for now. thanks for help. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi, I am also facing the same issue where ingress does not work but the load balancer does in GCP. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Strimzi supports Kubernetes Nginx Ingress using TLS passthrough which can be used to expose the broker on port 443. You can also create an internal listeners with customized advertised hosts and manage the Ingress resources for them yourself which allows you to use basically whatever you want to expose it. |
Beta Was this translation helpful? Give feedback.
All reactions
-
@scholzj A sample would help, can you please provide a sample ref what to change and where ? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm facing an issue service and ingress not create after apply "ingress listeners".
I follow this document.
K8S Tanzu
Ingress controller: Contour/Envoy
I'm not sure is this because I'm not use the Ingress Nginx or not? However, Ingress Contour also support TLS Pass through. Is there anything I can do with Strimzi and Ingress Contour
Beta Was this translation helpful? Give feedback.
All reactions