-
Notifications
You must be signed in to change notification settings - Fork 411
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
Enabling ipFamilies and ipFamilyPolicy #3087
Conversation
Signed-off-by: Yuri Sa <[email protected]>
Signed-off-by: Yuri Sa <[email protected]>
Signed-off-by: Yuri Sa <[email protected]>
looks like e2e is failing here |
Signed-off-by: Yuri Sa <[email protected]>
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.
Are these e2e tests checking anything a controller test wouldn't? I'd rather have that if you aren't going to check if ipv6 actually works. We could even add a controller test that sets all the optional attributes in OpenTelemetryCommonFields.
Other than that, LGTM.
Great idea, @swiatekm. I add the tests on both sides, controller and e2e. |
Signed-off-by: Yuri Sa <[email protected]>
e2e tests failed |
Signed-off-by: Yuri Sa <[email protected]>
Signed-off-by: Yuri Sa <[email protected]>
Signed-off-by: Yuri Sa <[email protected]>
Signed-off-by: Yuri Sa <[email protected]>
Signed-off-by: Yuri Sa <[email protected]>
Signed-off-by: Yuri Sa <[email protected]>
Signed-off-by: Yuri Sa <[email protected]>
Signed-off-by: Yuri Sa <[email protected]>
Description:
Enabling ipFamilies and ipFamilyPolicy to be configured via OpenTelemetryCollector
Link to tracking Issue(s):
Testing:
Documentation: