Skip to content
This repository has been archived by the owner on Jan 12, 2022. It is now read-only.

cortex: bump to current HEAD of master #655

Merged
merged 4 commits into from
May 3, 2021
Merged

cortex: bump to current HEAD of master #655

merged 4 commits into from
May 3, 2021

Conversation

jgehrcke
Copy link
Contributor

Signed-off-by: Dr. Jan-Philip Gehrcke <jp@opstrace.com>
Signed-off-by: Dr. Jan-Philip Gehrcke <jp@opstrace.com>
Latest head of master from April 30, 2021
The 1.9.0-rc0 tag is not on Docker Hub

Signed-off-by: Dr. Jan-Philip Gehrcke <jp@opstrace.com>
- postings_compression_enabled is not needed anymore,
  always enabled
- api.response_compression_enabled is the new way to
  set frontend.compress_responses

Signed-off-by: Dr. Jan-Philip Gehrcke <jp@opstrace.com>
@jgehrcke
Copy link
Contributor Author

jgehrcke commented May 3, 2021

I think there was no container image on Docker hub for v1.9.0-rc.0. Switched to using current head of master.

Adjusting config as of:

		2021-05-03 14:07:21	
error loading config from /etc/cortex/config.yaml: Error parsing config file: yaml: unmarshal errors:
2021-05-03 14:06:20	
  line 71: field postings_compression_enabled not found in type tsdb.IndexCacheConfig
2021-05-03 14:06:20	
  line 37: field compress_responses not found in type frontend.CombinedFrontendConfig

Relevant changelog entries:

[CHANGE] Blocks storage: removed the config option -blocks-storage.bucket-store.index-cache.postings-compression-enabled, which was deprecated in Cortex 1.6. Postings compression is always enabled. #4101

[CHANGE] Query Frontend: removed the config option -querier.compress-http-responses, which was deprecated in Cortex 1.6. You should use-api.response-compression-enabled instead. #4101

@jgehrcke jgehrcke changed the title cortex: bump to 1.9.0-rc.0 cortex: bump to current HEAD of master May 3, 2021
@jgehrcke jgehrcke merged commit ad59725 into main May 3, 2021
@jgehrcke jgehrcke deleted the jp/bump-cortex190 branch May 3, 2021 13:35
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant