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
NOTE: GitHub issues are reserved for bug reports only.
For anything else, please join the conversation
in Kong Nation https://discuss.konghq.com/c/kubernetes.
Summary
The Kong ingress controller does not detect the ingress resource for a service.
Kong Ingress controller version
0.14.0
Kubernetes version
Kubernetes v1.9.5
Environment
Cloud provider or hardware configuration: Local setup using kubespray
OS (e.g. from /etc/os-release): CentOS Linux 7
Kernel (e.g. uname -a): Linux node1 3.10.0-862.9.1.el7.x86_64 Status of controller? #1 SMP Mon Jul 16 16:29:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
NOTE: GitHub issues are reserved for bug reports only.
For anything else, please join the conversation
in Kong Nation https://discuss.konghq.com/c/kubernetes.
Summary
The Kong ingress controller does not detect the ingress resource for a service.
Kong Ingress controller version
0.14.0
Kubernetes version
Kubernetes v1.9.5
Environment
uname -a
): Linux node1 3.10.0-862.9.1.el7.x86_64 Status of controller? #1 SMP Mon Jul 16 16:29:36 UTC 2018 x86_64 x86_64 x86_64 GNU/LinuxWhat happened
I have a grafana service running in my k8s cluster and am able to access it without any issues using NodePort.
I installed kong using helm as follows
And added the following ingress
The ingress gets added without issues however Kong does not pick up the ingress and add it to the list of it's services
Expected behvaior
Kong should have picked up the new ingress and added the services for proxying the traffic to it
Steps To Reproduce
Same as what happened
The text was updated successfully, but these errors were encountered: