Skip to content
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

Operator ignores Thanos images specified in the CR #67

Open
4n4nd opened this issue May 7, 2021 · 1 comment · May be fixed by #70
Open

Operator ignores Thanos images specified in the CR #67

4n4nd opened this issue May 7, 2021 · 1 comment · May be fixed by #70

Comments

@4n4nd
Copy link
Contributor

4n4nd commented May 7, 2021

In my CR, I have tried setting the image for Thanos Components (Store/Compact/Receive/...) to quay.io/thanos/thanos:v0.20.1 or any other image but It always uses quay.io/thanos/thanos:v0.17.1.

@4n4nd
Copy link
Contributor Author

4n4nd commented May 7, 2021

I am not sure if this is relevant, but I see this in the Operator logs:

level=error ts=2021-05-07T17:12:06.680175023Z caller=resource.go:202 msg="sync failed" key=opf-observatorium/opf-observatorium err="failed to run step: 1 error occurred:\n\t* failed to execute action (CreateOrUpdate): discovering resource information failed for  in : groupVersion shouldn't be empty\n\n"
level=debug ts=2021-05-07T17:12:06.680346569Z caller=resource.go:211 msg="sync triggered" key=opf-observatorium/opf-observatorium
E0507 17:12:06.680280       1 resource.go:204] Sync "opf-observatorium/opf-observatorium" failed: failed to run step: 1 error occurred:
	* failed to execute action (CreateOrUpdate): discovering resource information failed for  in : groupVersion shouldn't be empty

@4n4nd 4n4nd linked a pull request May 20, 2021 that will close this issue
saswatamcode pushed a commit to saswatamcode/observatorium-operator that referenced this issue May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant