fix(ci): Use loopback ipv4 (127.0.0.1) for Kafka advertised listeners #922
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
beezz
force-pushed
the
integration-tests-kafka-update
branch
from
a14f3fc
to
3486015
Compare
RaduW
approved these changes
Feb 9, 2021
jan-auer
changed the title
beezz
force-pushed
the
integration-tests-kafka-update
branch
from
7290190
to
1e6b189
Compare
beezz
changed the title
jan-auer
added a commit
that referenced
this pull request
Feb 10, 2021
* master: fix(ci): Use loopback ip for advertised listeners (#922)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The new Docker version does not proxy the ipv6 loopback by default anymore. The GitHub actions virtual environment is adding an alias for localhost pointing to the ipv6 address which causes
librdkafkato resolvelocalhostinto two addresses and round-robin connections. With the recent update of docker in Ubuntu repositories, this mechanism is now broken (for the ipv6 address).Using 127.0.0.1 in advertised listeners will circumvent the IP resolution.
#skip-changelog