-
Notifications
You must be signed in to change notification settings - Fork 2.4k
[tempo-distributed] Add support to set specific Tempo gateway annotations #3692
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
[tempo-distributed] Add support to set specific Tempo gateway annotations #3692
Conversation
Signed-off-by: Garnaalkroket <robindroeck@gmail.com>
df77751
to
a319551
Compare
Hey @Garnaalkroket Please address the failed CI check, before we could proceed to merge this, Thank you! |
Signed-off-by: Garnaalkroket <robindroeck@gmail.com>
d54c05a
to
3247a08
Compare
I've updated the documentation and made a version bump, seeing as this is adding functionality that seems missed (as other deployments do have this feature) I opted for a patch version bump, please let me know if this should be a minor bump instead. |
@Garnaalkroket I believe you should go for a minor bump. |
Signed-off-by: Garnaalkroket <robindroeck@gmail.com>
Signed-off-by: Garnaalkroket <robindroeck@gmail.com>
I've changed the bump to a minor version |
This PR adds an annotations map (default empty) as part of the values for the gateway that allows for specifying annotations specific to the Tempo gateway deployment.
In order to comply with certain internal security standards it would be great to be able to specify annotations for the Tempo gateway deployment (now this is only possible for gateway pods). This functionality seems present for most other components (e.g.: distributor, compactor, querier) but seems left out for the gateway.