Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

health checks for orderer unreachable from kubelet: causing pod to crash #6

Open
gWOLF3 opened this issue Oct 1, 2019 · 1 comment
Assignees
Labels
bug Something isn't working minor this is a minor issue/enhancement

Comments

@gWOLF3
Copy link
Member

gWOLF3 commented Oct 1, 2019

health checks on the orderer are unreachable on the kubelet.

expected: should be reachable from kubelet. same health checks are working fine on peer.

whats happening?

health check is working fine when inside container but unreachable from kubelet. tested on both minikube and gke.

how to replicate: check out healthcheckv2 branch. this functionality was added in 1.4.1 fabric release/

@gWOLF3 gWOLF3 self-assigned this Oct 1, 2019
@gWOLF3 gWOLF3 added bug Something isn't working minor this is a minor issue/enhancement labels Oct 1, 2019
@gWOLF3
Copy link
Member Author

gWOLF3 commented Oct 3, 2019

this issue is FIXED. plus learned some really useful shit:

  1. port 8443 indeed does have conflicts with minikube api server. i tried changing with minikube start --apiserver-port <someotherport> command, but was still having trouble. this is not the best way anyhow.

  2. better way: change the address that healthchecks are exposed on in values file. this was tricky because i was using the wrong env variable, namely PEER_OPERATIONS_LISTENADDRESS - after a helpful discussion on rocket chat, I learned that these variables are leveraging viper's template engine - and the correct way to specify orderer is with ORDERER_OPERATIONS_LISTENADDRESS. anyways - more info on this - check out my convo on hyperledger rocket chat with user btl5037.

gWOLF3 pushed a commit that referenced this issue Oct 3, 2019
1) modified with raft's suggestions for PR (see comments on OG
healthchecks merge)

2) allowed for dynamic setting of operations port (useful when there is
some conflicts; ie with minikube - see issue #6 )
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working minor this is a minor issue/enhancement
Projects
None yet
Development

No branches or pull requests

1 participant