I have installed Kong using Kubernetes-ingress-controller using these steps. I am getting the following error when hit the Kong instance.
{"message":"failure to get a peer from the ring-balancer"}
Can anyone help me with this? Thanks in advance.
Kong could not connect to the upstream services, hence 503 error is returned.
Related
I am getting a 502 Gad Gateway nginx error returned from a couple of my applications to one single workstation which happens to be an Amazon Workspace workstation. These applications work flawlessly when accessing them from any other machine - including from a different Amazon Workspace. I can see the server side error being returned in the /var/log/nginx/access.log. I have another application that is set up pretty much identically that I can access fine from the Workspace in question. The 502 Bad Gateway shows up only after 4 or 5 minutes of loading. Any ideas? Thanks!
I am trying to setup an ingress-controller to a EKS cluster. I followed the nginx guide to deploy the nginx controller.
https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-manifests/
But the nginx ingress configuration file is not considering the "service ips" in the "upstream".
enter image description here
Any help!
Thanks in advance
After 2 days of debugging, I found the issue.
The "nginx-ingress" is unable to identify the "upstream service". Because the endpoint service is unable to locate the "App" due to "app" label was wrong.
It looks a silly manual mistake, but the debugging is not straight forward.
If anyone has similar issue, please try to debug with reference of below points:-
execute the "nginx-ingress" with logs enabled (v3)
Find the list of endpoints in the cluster.
If your upstream, showing a valid point then look the "nginx-ingress.conf"
If not, address the service endpoint issue first.
I am using openshift 4.5. I used service and routes and it is externally accessible. Application is working fine, but sometimes i am getting 502 error.
I am using ingress haproxy route.
Appreciate your thoughts on resolving this issue.
I have setup my web application and I saw my POD was successfully deployed, I have created HTTPS and HTTP route of the service. But when I hit the API, it gives sometime success or sometime 503 status code.
I do not see any issue in the POD and also I have setup health check.
Could anyone help me to resolve this issue.
POD Image :- jboss-webserver31-tomcat8-openshift:1.2
FYI- Right now I am using free version of the OpenShift.
Thanks,
Shailendra Soni
I am using the fabric8 library to create replication controllers on the kubernetes cluster. When I create areplication controller with the name rc-UUID.toString();
It errors aout with the following message
ReplicationController is forbidden. What does this indicate?
I don't think that the problem is the name.
Names like: rc-fa75ddfd-bea7-45b5-8d2f-ed806652b461 are valid.
Usually the message forbidden appears in one of the following cases:
i) http status code 401
ii) https status code 404
Error (i) appears when you are connecting to a remote Kubernetes Environment and can be solved by login in. Try kubectl login or oc login.
Error (ii) appears when the client is instantiated from within Kubernetes and the service account hasn't been properly configured.
Either way, I'd strongly encourage you to upgrade to a more recent version of the cabernets client, which has more meaningful error messages.
If none of my suggestion solves your issue, please attach the full output.
Cheers