-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Add support for additional storage backends in operator #5432
Add support for additional storage backends in operator #5432
Conversation
56e81d0
to
2b54f31
Compare
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.
Did a first pass of the source code but did not test this yet in any deployment. The change looks pretty straight-forward though, so I don't expect any surprises when testing.
2b54f31
to
cde4a57
Compare
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.
Nearly there, just some minor stuff and the question in loki-broker remaining.
3fcc269
to
8311977
Compare
8311977
to
ce42f92
Compare
What this PR does / why we need it:
This PR adds Azure, GCS, and Swift as storage options for the Loki Operator. Loki already provides support for these storage types and an easy configuration for multiple components through the
common_config
. This PR implements the usage of aObjectStorageSecretType
to allow the operator to understand what type of storage it will be utilizing. Like the existing storage configuration, the human operator would need to know what components need to be in the secret for Loki to be able to access the storage.Which issue(s) this PR fixes:
Fixes #4974
Special notes for your reviewer:
Local File System was left out of this PR as it didn't make sense to have a path directory in a secret.
Checklist
CHANGELOG.md
about the changes.