I am trying to add Kubernetes Ingress Controller for Kong 0.14.1) using Cassandra as DB. What concepts should I known before going this path, and is there a plan to provide support for 0.14.1. All the article point to using 0.13.X for best results but I cannot get cassandra working with anything older than 0.14.1.
The deployment succeeds but I do not see Ingress Controller.
Appreciate any help. NOTE: I have used Kong 0.14.1.
Here are the additional lines added to my Kong Values.yaml:
Kong Ingress Controller’s primary purpose is to satisfy Ingress resources
created in k8s. It uses CRDs for more fine grained control over routing and
Happy to see that you are trying to use Kong Ingress Controller with Cassandra.
Kong Ingress Controller currently doesn’t support Kong 0.14.1. The support for 0.14.1 is ready but not yet released. Stay tuned for more updates on that. Meanwhile, you can use Kong 0.13.x for your use.
Regarding, controller not coming up, could you share (Github Gist, etc) the deployment that you used to deploy Cassandra, Kong in data plane mode and control-plane pod? Could you share any logs that might help us resolve this issue?
The Helm chart for Kong doesn’t deploy Kong as an Ingress Controller but as an application on Kubernetes.
There is a PR in works to support this use case in future.
Meanwhile, you can deploy Kong for your k8s Ingress using our Deployment files.
It seems like you’ve not read our docs and I would encourage you to go through them and try out the getting started guide:
I’d be happy to answer any specific questions you may come across.
Now this Service 1 is sitting in a different name space as Kong
Kong Ingress Controller is complaining:
W0912 17:17:05.473216 7 kong.go:218] the service defined in the ingress kong/ocnrf-ingress does not exists
W0912 17:17:05.478117 7 kong.go:620] the service defined in the ingress kong/ocnrf-ingress does not exists
How do we tell Kong Ingress about service path to a service sitting in different name space? do we need additional configuration? The serivce1 is using NodePort type of service…
Please let me know if I am missing something or is it something to do with our internal kubernetes networking?
I have updated the host as ‘kong-proxy’ in my ingress rule and I still get 404 back from proxy…it seems like my proxy is not able to hook to the Ingress rule and forward to Service in the back end…
In the spirit of helping other community members, could you share the solution that worked for your problem and then mark this post as “Solved”. Thanks in advance!
Fixes:
a. Include host in ingress rules.
b. Set the proxy port to accept connection on port 80
c. Add the rules as mentioned:
d. make the Kong Ingress controller and Kong to be deployed as infrastructure service rather than tying to individual clusters.
Potentially will work on Kong Ingress Controller 0.2.0 and get it working with Kong 0.14.1. Will keep the team posted.