Experimental TSDB: Enable Azure Storage Backend #2083
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Ken Haines <[email protected]>
khaines
force-pushed
the
khaines/tsdb-azure-storage
branch
3 times, most recently
from
b9262ea to
ef78ab8
Compare
khaines
force-pushed
the
khaines/tsdb-azure-storage
branch
from
579be55 to
956205c
Compare
Signed-off-by: Ken Haines <[email protected]>
Signed-off-by: Ken Haines <[email protected]>
khaines
force-pushed
the
khaines/tsdb-azure-storage
branch
from
956205c to
1e5679a
Compare
Signed-off-by: Ken Haines <[email protected]>
|
Thanks for the attention to detail on the documentation @pracucci ! |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does: Adds the needed cortex structs and configuration to enable azure storage usage with the experimental tsdb engine.
I've got a small cluster using this currently as it's storage backend, but it's still relatively new so I would say testing for this over the long term is still ongoing.
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]