This got resolved after I restarted the ingress ctl pods.
On Monday, September 25, 2017 at 4:27:08 PM UTC-4, Vaibhav Dharmendra
Rajadhyaksha wrote:
>
> Hello All,
>
> I have setup an ingress to access my controller service. I was able to set
> it up correctly and hit the endpoint, but started getting timeout errors
> after a certain time. I am able to successfully curl the service from
> another pod. Below is how my ingress looks. We have istio sidecar proxy in
> place for the deployments(Istio auth- disabled). I have tried setting it up
> for a couple other services as well and am running into the same issue.
>
> apiVersion: extensions/v1beta1
> kind: Ingress
> metadata:
> annotations:
> ingress.bluemix.net/rewrite-path: serviceName=fusion--controller
> rewrite=/
> name: fusion-controller
> spec:
> rules:
> - host: apiconnect-dev-1.us-south.containers.mybluemix.net
> http:
> paths:
> - backend:
> serviceName: fusion--controller
> servicePort: 3082
> path: /fusion/controller/
> status:
> loadBalancer: {}
>
> /opt/ibm/app # curl -s http://controller:3082
>
> {"started":"2017-09-25T20:05:59.379Z","uptime":968.755}/opt/ibm/app #
>
> Any suggestions on what might be the issue.
>
> Thanks.
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.
