Skip to content

update zero health check for dgraph-ha.yaml #5580

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

Merged
merged 1 commit into from
Jun 17, 2020

Conversation

darkn3rd
Copy link
Contributor

@darkn3rd darkn3rd commented Jun 5, 2020

Discovered issue with dgraph-ha.yaml where dgraph cluster may not come back to a healthy state when zero has a readinessProbe.httpGet.path set to /state. Changing this value to /health.

Fixes #5583.


This change is Reviewable

@darkn3rd darkn3rd requested a review from danielmai June 5, 2020 00:54
@github-actions github-actions bot added the area/integrations Related to integrations with other projects. label Jun 5, 2020
Copy link
Contributor

@danielmai danielmai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewed 1 of 1 files at r1.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved

Copy link
Contributor

@martinmr martinmr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewable status: :shipit: complete! all files reviewed, all discussions resolved

@darkn3rd darkn3rd merged commit 88c0a18 into master Jun 17, 2020
@darkn3rd darkn3rd deleted the joaquin/k8s-ha-readiness-update branch June 17, 2020 22:18
dna2github pushed a commit to dna2fork/dgraph that referenced this pull request Jul 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/integrations Related to integrations with other projects.
Development

Successfully merging this pull request may close these issues.

Kubernetes Zero group never reaches ready state after restart
3 participants