-
Notifications
You must be signed in to change notification settings - Fork 4.8k
CORENET-6232: add PreconfiguredUDNAddresses FG tests #30010
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
Changes from all commits
8fa5902
6bc9d9c
cd54e49
b106650
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1890,6 +1890,12 @@ type networkAttachmentConfigParams struct { | |
role string | ||
} | ||
|
||
// workloadNetworkConfig contains workload-specific network customizations | ||
type workloadNetworkConfig struct { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe it makes sense to "prepare" for the future and assume we want to one day have multiple of these. For that, you'd have to add here the workload name. If we ever want to extend this to pods (god forbid) we might actually have to add the resource type as well. Anyway, I'm digressing ... We can postpone it until it is actually needed. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yes let's postpone until we know more. |
||
preconfiguredIPs []string | ||
preconfiguredMAC string | ||
} | ||
|
||
type networkAttachmentConfig struct { | ||
networkAttachmentConfigParams | ||
} | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you need to use
ToUpper
? It is perfectly able to parse macs with lowercased valid hex characters (a through F).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
at the end we're comparing strings:
{@.status.interfaces[0].mac}
gives the MAC in lower case, we compare it to the MAC string with upper. I aligned them to work fluently, but we can instead input MACs with lower case..There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see ! OK, we're good.
Maybe it would be preferable to actually compare macs instead, but this solution is OK for me.