azure: Add the correct JSON tag to GatewayIP field in CiliumNode CRD#15182
Merged
aanm merged 2 commits intocilium:masterfrom Mar 9, 2021
AnishShah:azure-ipam
Merged
azure: Add the correct JSON tag to GatewayIP field in CiliumNode CRD#15182aanm merged 2 commits intocilium:masterfrom AnishShah:azure-ipam
aanm merged 2 commits intocilium:masterfrom
AnishShah:azure-ipam
Conversation
aanm
requested changes
Mar 3, 2021
aanm
approved these changes
Mar 4, 2021
christarazi
approved these changes
Mar 4, 2021
Contributor
Author
|
Adding DO NOT MERGE tag because I haven't got chance to test the second commit on my Azure cluster. |
Member
You can convert the PR into draft mode to indicate that it's WIP. |
ti-mo
reviewed
Mar 5, 2021
The incorrect JSON tag "-" was added to GatewayIP field in commit 8de6dc5 that was causing GatewayIP field to not get populated in CiliumNode CRD. Signed-off-by: Anish Shah <anishshah@google.com>
The JSON tag for GatewayIP field does not follow the same convention as other field. Inorder to have the same consistency across all JSON tags, we introduce Gateway field and deprecate GatewayIP field. Signed-off-by: Anish Shah <anishshah@google.com>
Contributor
Author
|
Tested it on my cluster that this works |
Member
|
test-me-please Edit: netnext hit #15246 |
Contributor
Author
|
Looks like there's a flaky test. |
Member
|
test-1.13-netnext |
Member
|
hit #15246 |
HadrienPatte
added a commit
that referenced
this pull request
Apr 2, 2026
Remove deprecated fields that have been unused for 5+ years: * Azure `AzureInterface.GatewayIP` (obsolete since v1.10, see #15182) * AWS `ENISpec.InstanceID` (obsolete since v1.8, see #10569) * AWS `ENISpec.{MinAllocate,PreAllocate,MaxAboveWatermark}` (obsolete since v1.8, see #10089) Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
HadrienPatte
added a commit
that referenced
this pull request
Apr 2, 2026
Remove deprecated fields that have been unused for 5+ years: * Azure `AzureInterface.GatewayIP` (obsolete since v1.10, see #15182) * AWS `ENISpec.InstanceID` (obsolete since v1.8, see #10569) * AWS `ENISpec.{MinAllocate,PreAllocate,MaxAboveWatermark}` (obsolete since v1.8, see #10089) Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
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
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.
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXXline if the commit addresses a particularGitHub issue.
The incorrect JSON tag "-" was added to GatewayIP field in commit 8de6dc5
that was causing GatewayIP field to not get populated in CiliumNode CRD.
Since GatewayIP field was not populated, Cilium CNI was creating incorrect
ip rules and routesthat was affecting pod-to-pod connectivity.