Kafka-ui not loading on Kubernetes/Rancher

[cetinkesepara]

Hi,
I can use Kafka-ui on Docker. But when I build it on Kubernetes with Rancher, the page doesn't load.

It is constantly loading as below.

Console output

What is the problem?

[Haarolean]

Hi, the issue seems definitely in your configuration. Considering that your app is somehow located at xx:8080/proxy and there is a bunch of 404s, I suggest you haven't set the SERVER_SERVLET_CONTEXT_PATH variable.

Also, check out this issue, this might help.

[cetinkesepara]

This didn't help me. I reach the page you see with the Cluster IP service. No Ingress has yet been defined. So it's normal to see it as xx:8080/proxy. Only when I go to this page, it cannot pull the data in it somehow.

I can also access xx:8080/proxy/actuator, xx:8080/proxy/actuator/info.

There is currently no Kafka Environment in the Pod settings. I just want to see a blank UI page.

The image below is the Kafka-ui image I'm running with Docker. I can't get this result in Kubernetes.

[Haarolean]

/cc: @5hin0bi @azatsafin any ideas?

[cetinkesepara]

@5hin0bi
Network:

clusters:
kind: "Status", apiVersion: "v1", metadata: {}, status: "Failure",…} apiVersion: "v1" code: 404 details: {} kind: "Status" message: "the server could not find the requested resource" metadata: {} reason: "NotFound" status: "Failure"

Manifest:
{type: "error", status: "401", message: "Unauthorized 401: must authenticate"} message: "Unauthorized 401: must authenticate" status: "401" type: "error"

Pod Log: There is currently no Kafka Environment in the Pod settings. I just want to see a blank UI page.

[5hin0bi]

@cetinkesepara thank you for the provided information.

Let me try to conclude on what we see here:

1. Basing on the Network tab information - URLs that were requested differ by size. The first is much longer than the second. This should not be like this. First URL contains port, second one does not.
   The first request targets 8080/proxy, the second targets the URL without /proxy path. The reason is that the application is most likely not ready to work with the /proxy path. To solve it you may set SERVER_SERVLET_CONTEXT_PATH=/proxy as @Haarolean suggested before. This will tell the application to return currently not found manifest.json and /api/clusters by the /proxy path.

2. Since our helm chart provides the possibility to use ingress you can try to use it. This can resolve your problem as well.

I hope this helps. In case of any further questions please let us know.

[cetinkesepara]

@5hin0bi Thanks but it didn't work. I did what you said. This time, I was able to reach the same page as follows.

:8080/proxy/proxy/

[5hin0bi]

@cetinkesepara what do you see on the F12 Network tab now? Can you please attach a screenshot again?

Can you try to access Kafka-UI via Kafka-UI service port-forwarding? Will it work?
I've taken a look at the k8s configuration in the demo env we have and SVC for Kafka-UI is of the Cluster IP type and works fine. I don't have to use /proxy path.
Is it possible to see your SVC yaml file?

Please let me know.

[cetinkesepara]

@5hin0bi
First of all, we use Rancher for Kubernetes. While creating the pod, I pull the image here "https://hub.docker.com/r/provectuslabs/kafka-ui" and opened port 8080. Then I set up a Cluster_ip service and connected it to the Pod.

I can't deal with this anymore. Thanks for your help.