Build Pod SNAT: remove risk of adding nil pointer and later panicking #4150
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
We cannot always depend on there being an external IP family that matches the pod IP family. For example, if we are converting from dualstack to single stack. In that scenario, a panic may occur because we depend on non-nil entries within the nat slices. Signed-off-by: Martin Kennelly <mkennell@redhat.com>
martinkennelly
requested review from
trozet,
dcbw,
girishmg,
jcaamano and
tssurya
as code owners
jcaamano
approved these changes
Feb 14, 2024
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.
We cannot always depend on there being an external IP family that matches the pod IP family.
For example, if we are converting from dualstack to single stack. In that scenario, a panic may occur because we depend on non-nil entries within the nat slices.
- What this PR does and why is it needed
- Special notes for reviewers
- How to verify it
- Description for the changelog