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

fix(injector) change local address for probes #660

Merged
merged 3 commits into from
Apr 6, 2020

Conversation

lobkovilya
Copy link
Contributor

Summary

kuma-dp refuses to work on Kind after updating Envoy up to 1.13.1, current PR fixes that issue

Readiness and liveness probes didn't work as expected and failed with: Readiness probe failed: wget: can't connect to remote host: Connection refused.

For some reason, localhost resolves to 127.0.0.1 on envoy-alpine 1.12.2 and resolves to ::1 on further versions.

According to envoy source code, admin server listener starts at 0.0.0.0:9901 so it binds to IPv4 interface. So in order to avoid ambiguous behavior, makes sense to change localhost to 127.0.0.1

@lobkovilya lobkovilya requested a review from a team April 3, 2020 22:53
Copy link
Contributor

@jakubdyszkiewicz jakubdyszkiewicz left a comment

Choose a reason for hiding this comment

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

add a changelog please

@lobkovilya lobkovilya merged commit 5479a0a into master Apr 6, 2020
tharun208 pushed a commit to tharun208/kuma that referenced this pull request Apr 6, 2020
* fix(injector) change local address for probes

* fix(injector) fix injector tests

* fix(injector) add CHANGELOG
tharun208 pushed a commit to tharun208/kuma that referenced this pull request Apr 6, 2020
* fix(injector) change local address for probes

* fix(injector) fix injector tests

* fix(injector) add CHANGELOG
@lobkovilya lobkovilya deleted the fix/probes-local-address branch May 1, 2020 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants