-
Notifications
You must be signed in to change notification settings - Fork 30
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
Update tempo to 2.5.0 #958
Changes from all commits
e2a68a0
906843c
53c6e7e
e8b3a2f
5b67d47
edbc377
ac85d99
4554d6a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' | ||
change_type: breaking | ||
|
||
# The name of the component, or a single word describing the area of concern, (e.g. operator, github action) | ||
component: operator | ||
|
||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
note: Update Tempo to 2.5.0 | ||
|
||
# One or more tracking issues related to the change | ||
issues: [958] | ||
|
||
# (Optional) One or more lines of additional information to render under the primary note. | ||
# These lines will be padded with 2 spaces and then inserted directly into the document. | ||
# Use pipe (|) for multiline entries. | ||
subtext: | | ||
Upstream Tempo 2.5.0 image switched user from `root` to `tempo` (10001:10001) and ownership of `/var/tempo`. | ||
Therefore ingester's `/var/tempo/wal` created by previous deployment using Tempo 2.4.1 needs to be updated and | ||
changed ownership. The operator upgrades the `/var/tempo` ownership by deploying a `job` with `securityContext.runAsUser(0)` | ||
and it runs `chown -R /var/tempo 10001:10001`. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
# Current Operator version | ||
OPERATOR_VERSION ?= 0.10.0 | ||
TEMPO_VERSION ?= 2.4.1 | ||
TEMPO_QUERY_VERSION ?= 2.4.1 | ||
TEMPO_VERSION ?= 2.5.0 | ||
TEMPO_QUERY_VERSION ?= 2.5.0 | ||
TEMPO_GATEWAY_VERSION ?= main-2024-05-29-ca8d2de | ||
TEMPO_GATEWAY_OPA_VERSION ?= main-2024-04-29-914c13f | ||
OAUTH_PROXY_VERSION=4.12 | ||
|
@@ -159,7 +159,7 @@ run: manifests generate ## Run a controller from your host. | |
|
||
.PHONY: docker-build | ||
docker-build: ## Build docker image with the manager. | ||
docker buildx build --load --platform linux/${ARCH} --build-arg OPERATOR_VERSION -t ${IMG} . | ||
docker buildx build --load --platform linux/${ARCH} --build-arg OPERATOR_VERSION --build-arg TEMPO_VERSION -t ${IMG} . | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. afaics we don't need to pass There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That does not work for e.g.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah, yes, but this is only required for testing, right? Anyway, still useful 👍 |
||
|
||
.PHONY: docker-push | ||
docker-push: ## Push docker image with the manager. | ||
|
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.
@rubenvp8510 do you know how
OPERATOR_VERSION
is passed in GHA when the image is published? We might need to update the workflow to include the tempo version