此内容没有您所选择的语言版本。

Appendix E. Gluster Block Storage as Backend for Logging and Metrics


Following section guides to configure Gluster Block Storage as the backend storage for logging and metrics

Note

Block volume expansion is not supported in CNS 3.6. Administrators are required to do proper capacity planning while using Gluster Block as backend storage when using dynamic provisioning.

E.1. Prerequisites

Before setting gluster block storage as the backend for logging or metrics, check if the following prerequisites are met:
  • In the storageclass file, check if the default storage class is set to the storage class of gluster block. For example:
    # oc get storageclass
    NAME                TYPE
    gluster-block        gluster.org/glusterblock
    Copy to Clipboard Toggle word wrap
  • If the default is not set to gluster-block (or any other name that you have provided) then execute the following command. For example:
    # oc patch storageclass gluster-block -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
    Copy to Clipboard Toggle word wrap
    • Execute the following command to verify:
      oc get storageclass
      NAME                     TYPE
      gluster-block (default)   gluster.org/glusterblock
      Copy to Clipboard Toggle word wrap
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat