-
Notifications
You must be signed in to change notification settings - Fork 344
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
Enable annotations to be specified with the deployable components #86
Conversation
Signed-off-by: Gary Brown <[email protected]>
Was also going to add to ingress - but the code that creates the Ingress doesn't know whether it was called from all-in-one or query - so would not know which part of the supplied JaegerSpec to look at. Think the ingress definition (spec) needs to be pulled out from the all-in-one and query and made a separate part of the spec, as it is independent on the deployment strategy used. |
Codecov Report
@@ Coverage Diff @@
## master #86 +/- ##
==========================================
+ Coverage 99.34% 99.35% +<.01%
==========================================
Files 18 18
Lines 769 777 +8
==========================================
+ Hits 764 772 +8
Misses 5 5
Continue to review full report at Codecov.
|
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. It can be merged as is, but I'd prefer to have one small change to the tests, where the test overrides an annotation that is implicitly added (like, prometheus.io/scrape
).
pkg/deployment/agent_test.go
Outdated
|
||
assert.Equal(t, "false", ds.Spec.Template.Annotations["sidecar.istio.io/inject"]) | ||
assert.Equal(t, "false", dep.Spec.Template.ObjectMeta.Annotations["sidecar.istio.io/inject"]) |
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: ObjectMeta
is embedded into the Template
, you don't need to reference it explicitly.
pkg/deployment/agent_test.go
Outdated
|
||
assert.Equal(t, "false", ds.Spec.Template.Annotations["sidecar.istio.io/inject"]) | ||
assert.Equal(t, "false", dep.Spec.Template.ObjectMeta.Annotations["sidecar.istio.io/inject"]) |
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.
Could you also add a test where you override an annotation that we set implicitly, like prometheus.io/scrape
? The code in this PR makes me believe that a user is able to set this to false
, so, having a test that explicitly tests this behavior would also serve as documentation.
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.
Reviewed 9 of 9 files at r1.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @jpkrohling)
Signed-off-by: Gary Brown <[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.
Reviewed 4 of 4 files at r2.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @jpkrohling)
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.
Reviewable status: complete! all files reviewed, all discussions resolved
Provides a more general way to define annotations, instead of specific approach used in #81.
Signed-off-by: Gary Brown [email protected]