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

Loopback interface on GKE cluster does not have IPv6 configuration #431

Open
VitalyGushin opened this issue Feb 28, 2024 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@VitalyGushin
Copy link

Loopback interface on GKE cluster does not have IPv6 configuration.
This causes that in examples using IPv6, client cannot ping itself via IPv6.
At the same time there are no problems with inter-service pings.
And the problem only reproducible on the GKE cluster.

@edwarnicke Should we try to fix this (via cluster configuration or hacks in SDK), or should we just ignore the self-ping scenario?

@VitalyGushin VitalyGushin added the bug Something isn't working label Feb 28, 2024
@VitalyGushin VitalyGushin self-assigned this Feb 29, 2024
@VitalyGushin VitalyGushin moved this to Blocked in Release v1.13.0 Feb 29, 2024
@VitalyGushin VitalyGushin moved this from Blocked to Todo in Release v1.13.0 Mar 13, 2024
@VitalyGushin VitalyGushin removed their assignment Mar 13, 2024
@denis-tingaikin denis-tingaikin moved this to Moved to next release in Release v1.14.0 Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Moved to next release
Status: No status
Development

No branches or pull requests

2 participants