-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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] Support initContainers and extraContainers for compactor #3391
Conversation
@zanhsieh this PR is based on the main branch, we should close it then right ? |
@Sheikh-Abubaker |
@zanhsieh @Sheikh-Abubaker I've rebased the PR to the latest |
Signed-off-by: Andy Lo-A-Foe <[email protected]>
Signed-off-by: MH <[email protected]> Signed-off-by: MH <[email protected]>
Signed-off-by: MH <[email protected]> Signed-off-by: MH <[email protected]>
@@ -54,6 +54,8 @@ spec: | |||
hostAliases: | |||
{{- toYaml . | nindent 8 }} | |||
{{- end }} | |||
initContainers: | |||
{{- toYaml .Values.ingester.initContainers | nindent 8 }} |
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 is a bug.
It should have been
- {{- toYaml .Values.ingester.initContainers | nindent 8 }}
+ {{- toYaml .Values.compactor.initContainers | nindent 8 }}
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.
Will be fixed in this PR: #3552 , thx!
We have a use case where we need to run an init container and extra container as part of the compactor pod.