Docs: Fix list of Ruler supported storages (#5008)

* Fix list of Ruler supported storages. * Update number of supported storages
3 years ago · ffd9e29486
parent 2b96e27fe1
commit ffd9e29486
1 changed files with 1 additions and 1 deletions
--- a/docs/sources/rules/_index.md
+++ b/docs/sources/rules/_index.md
@ -253,7 +253,7 @@ ruler:

 ## Ruler storage

-The Ruler supports six kinds of storage: configdb, azure, gcs, s3, swift, and local. Most kinds of storage work with the sharded Ruler configuration in an obvious way, i.e. configure all Rulers to use the same backend.
+The Ruler supports five kinds of storage: azure, gcs, s3, swift, and local. Most kinds of storage work with the sharded Ruler configuration in an obvious way, i.e. configure all Rulers to use the same backend.

 The local implementation reads the rule files off of the local filesystem. This is a read-only backend that does not support the creation and deletion of rules through the [Ruler API](../api/#ruler). Despite the fact that it reads the local filesystem this method can still be used in a sharded Ruler configuration if the operator takes care to load the same rules to every Ruler. For instance, this could be accomplished by mounting a [Kubernetes ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/) onto every Ruler pod.