Fix the IP family conversion with the unified image if the IP family was unset #2369
Conversation
This file contains hidden or 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
Result of fdb-kubernetes-operator-pr on Linux RHEL 9
|
nicmorales9
approved these changes
Sep 23, 2025
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.
Description
When converting to IP family 6 from unset (and assuming that the used IP address is IPv4), the unified image is currently not able to migrate to the new IP family and the operator will be stuck and requires manual interaction because some of the methods already try to access the IPv6 address which will be absent for the older pods. The idea was to make use of the "old" IP family if present (pods will be replaced anyways when the IP family changes).
Type of change
Please select one of the options below.
Discussion
I sneaked in the
Claude.md(the file was generated by Claude and might need some fine tuning).Testing
Running e2e tests and doing some manual tests since our e2e test setup doesn't have dual stack.
Documentation
Follow-up