Lex Rivera
Lex Rivera
Yep, package doesn't exist in debian stable. Probably can switch to pip installation if uvloop greatly helps with performance.
Open to suggestions. /var/tempo is ephemeral anyway since it was writing in-pod, so switching it to emptyDir should pose no issues?
Should we also set default securitycontext, like it's done in mimir and loki charts? I run mine with ``` - tempo: securityContext: capabilities: drop: - ALL readOnlyRootFilesystem: true runAsNonRoot: true...
> > In tempo-query-frontend pod, in tempo-query container, following error is present: > > ``` > > 2022-08-07T14:09:06.263Z [ERROR] tempo-query: plugin init error: error="open /tmp/plugin164587256: read-only file system" timestamp=2022-08-07T14:09:06.263Z >...
seems like i need to split podSecurityContext and containerSecurityContext
Since fsGroup can't be used at container level, i added podSecurityContext for fsGroup. But since we now have pod-wide securityContext, maybe it will be better to move other settings to...
Rebased. @joe-elliott can you talk a look please?
Might be nice idea to kick pipelines again. I'm not sure if resolving conflicts via github UI triggers builds.
Added /var/tempo emptydir to distirbutor as well - noticed it's required for 1.5. Shouldn't hurt.
@joe-elliott i reverted adding store to distributor as discussed here https://github.com/grafana/tempo/issues/1648 Should be ready to merge now, i think.