aws-samples / aws-microservices-deploy-options

This repo contains a simple application that consists of three microservices. Each application is deployed using different Compute options on AWS.
MIT No Attribution
429 stars 179 forks source link

"hello" greeting service is reported not healthy #239

Open arun-gupta opened 6 years ago

arun-gupta commented 6 years ago

Follow the steps at:

https://github.com/aws-samples/aws-microservices-deploy-options#deployment-canary-deployment-with-istio

Multiple invocations of the webapp endpoint shows that the hello greeting service is not healthy. Here is the output:

~ $ curl http://$(kubectl get svc/webapp -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
no healthy upstream Sheldon~ $ curl http://$(kubectl get svc/webapp -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
Howdy Sheldon~ $ curl http://$(kubectl get svc/webapp -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
Howdy Sheldon~ $ curl http://$(kubectl get svc/webapp -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
Howdy Sheldon~ $ curl http://$(kubectl get svc/webapp -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
Howdy Sheldon~ $ curl http://$(kubectl get svc/webapp -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
Howdy Sheldon~ $ curl http://$(kubectl get svc/webapp -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
Howdy Sheldon~ $ curl http://$(kubectl get svc/webapp -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
no healthy upstream Sheldon~ $ curl http://$(kubectl get svc/webapp -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
no healthy upstream Sheldon~ $ curl http://$(kubectl get svc/webapp -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
Howdy Sheldon~ $ curl http://$(kubectl get svc/webapp -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
no healthy upstream Sheldon~ $ curl http://$(kubectl get svc/webapp -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
christian-posta commented 6 years ago

What version of Istio are you using @arun-gupta ? I've got this running locally with istio 0.7.1, works great. I did experience similar issues to what you described with 0.7.0

image

arun-gupta commented 6 years ago

@christian-posta 0.7.1 only

$ ./bin/istioctl version
Version: 0.7.1
GitRevision: 62110d4f0373a7613e57b8a4d559ded9cb6a1cc8
User: root@c5207293dc14
Hub: docker.io/istio
GolangVersion: go1.9
BuildStatus: Clean
christian-posta commented 6 years ago

is the env exposed somewhere that i can take a look?

On Tue, Apr 17, 2018 at 2:17 PM, Arun Gupta notifications@github.com wrote:

@christian-posta https://github.com/christian-posta 0.7.1 only

$ ./bin/istioctl version Version: 0.7.1 GitRevision: 62110d4f0373a7613e57b8a4d559ded9cb6a1cc8 User: root@c5207293dc14 Hub: docker.io/istio GolangVersion: go1.9 BuildStatus: Clean

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aws-samples/aws-microservices-deploy-options/issues/239#issuecomment-382149631, or mute the thread https://github.com/notifications/unsubscribe-auth/AADP0W5tRL1OifYMGl5Kd5wHljnepRa2ks5tplvWgaJpZM4TVpMN .

-- Christian Posta twitter: @christianposta http://blog.christianposta.com http://www.christianposta.com/blog

arun-gupta commented 6 years ago

Kops cluster is created as shown at https://github.com/aws-samples/aws-microservices-deploy-options#deployment-create-cluster-using-kops

What can I give to expose the environment?

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6",
GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean",
BuildDate:"2018-03-21T20:49:26Z", GoVersion:"go1.9.4", Compiler:"gc",
Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.7",
GitCommit:"b30876a5539f09684ff9fde266fda10b37738c9c", GitTreeState:"clean",
BuildDate:"2018-01-16T21:52:38Z", GoVersion:"go1.8.3", Compiler:"gc",
Platform:"linux/amd64"}
cdenneen commented 6 years ago

@arun-gupta any updates?