-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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 bookinfo MongoDB sample app on IPv6 cluster #53072
Conversation
😊 Welcome @mkralik3! This is either your first contribution to the Istio istio repo, or it's been You can learn more about the Istio working groups, Code of Conduct, and contribution guidelines Thanks for contributing! Courtesy of your friendly welcome wagon. |
|
Hi @mkralik3. Thanks for your PR. I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/ok-to-test |
/test release-notes |
* upstream/master: ambient: fix add+remove+add of iptables (istio#53063) Apply missing secret filter for discoverySelector (istio#53175) ambient: only set app tunnel if configured (istio#53155) Automator: update proxy@master in istio/istio@master (istio#53173) Fix bookinfo MongoDB on IPv6 cluster (istio#53072)
Please provide a description of this PR:
Mongo DB from bookinfo samples doesn't work on IPv6 cluster ( tried on kind IPv6 only). It seems that the Mongo port is not bind correctly.
The
ratings-v2
pod contains the error:Reproducer with Kind IPv6 cluster: https://gist.github.com/mkralik3/815392209af83e8861293a27994c4e0b
Fix:
Added
--ipv6
and--bind_ip_all
args to the Mongo DB container.Now, the mongo pod is able to bind IPv6 and IPv6, see the log:
Ref.: https://www.mongodb.com/docs/manual/core/security-mongodb-configuration/#ip-binding-in-self-managed-deployments
Tested on both IPv6 only and IPv4 only kind clusters and bookinfo app with ratings-v2 mongo db works correctly (see my reproducer above)