-
Notifications
You must be signed in to change notification settings - Fork 444
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
Create service for extensions #3403
base: main
Are you sure you want to change the base?
Conversation
df4a731
to
3a5a2ee
Compare
3a5a2ee
to
3ab8c98
Compare
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.
great progress,
Please add unit tests and e2e test
d742325
to
eb14bf7
Compare
eb14bf7
to
5f26d14
Compare
007c7eb
to
d9ff5df
Compare
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.
This looks good to me overall, left a few comments and questions.
41da859
to
5e26224
Compare
5e26224
to
4f27a6b
Compare
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 wanted to be clearer about how I'd like the e2e test you added to look like. I'm including some suggestions to help demonstrate that. Fundamentally, the manifests we assert against should only contain attributes that are relevant to this specific test.
The rest of this PR looks good to me, nicely done. 👍
c5d4b40
to
effe1d9
Compare
d25d89a
to
0091576
Compare
@@ -321,6 +321,161 @@ func TestMonitoringService(t *testing.T) { | |||
}) | |||
} | |||
|
|||
func TestExtensionService(t *testing.T) { |
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.
nit... can you change this to be a list test instead here and also assert on the service created to be sure it has the right ports set?
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.
Okay, I understood about asserting the ports. But can you elaborate more on list test instead
? Do you mean something like this:
func TestExtensionService(t *testing.T) {
tests := []struct{
name. string
params manifests.params
ports []corev1.ServicePort
expectedErr error
}{
{
....
....
},
{
....
....
},
}
for _,tc := range tests {
t.Run(tc.name, func (t *testing.T){
// assertion
})
}
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.
yep! you can see an example here for these.
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 have added the changes. Kindly review them!
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.
@jaronoff97 @iblancasa @swiatekm if the changes looks good, then can we merge this one please?
0091576
to
b90db6c
Compare
be77545
to
6751006
Compare
Signed-off-by: Ankit152 <[email protected]>
Signed-off-by: Ankit152 <[email protected]>
Signed-off-by: Ankit152 <[email protected]>
Signed-off-by: Ankit152 <[email protected]>
6751006
to
c3ebb64
Compare
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.
LGTM, thank you for the contribution!
Description:
The Otel Operator doesn't creates a service for extensions. This will help the operator to create Service for extensions which will be consumed by an Ingress so that users can interact with it directly. This is related to deployment of Jaeger V2 in k8s.
Link to tracking Issue(s):
Testing:
Documentation: