You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Backend service type is cluster ip and checked can be accessed in K8S
/]# curl ollama.ollama:11434 -v
* Rebuilt URL to: ollama.ollama:11434/
* Trying 192.168.1.153...
* TCP_NODELAY set
* Connected to ollama.ollama (192.168.1.153) port 11434 (#0)
> GET / HTTP/1.1
> Host: ollama.ollama:11434
> User-Agent: curl/7.61.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: text/plain; charset=utf-8
< Date: Wed, 27 Nov 2024 03:13:58 GMT
< Content-Length: 17
<
* Connection #0 to host ollama.ollama left intact
I checked router and upstream, seems KIC creater two rules with one router. But my Gateway just have one pod. I don't know if that has anything to do with it.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
No response
Expected Behavior
No response
Steps To Reproduce
Kong Ingress Controller version
Kubernetes version
Anything else?
Backend service type is cluster ip and checked can be accessed in K8S
I checked router and upstream, seems KIC creater two rules with one router. But my Gateway just have one pod. I don't know if that has anything to do with it.
The text was updated successfully, but these errors were encountered: