OBSDOCS-94 - Correcting storage for Loki

[libander]

Version(s): 4.12+

Issue: OBSDOCS-94

Link to docs preview:

• https://68232--docspreview.netlify.app/openshift-enterprise/latest/scalability_and_performance/optimization/optimizing-storage#available-persistent-storage-options_persistent-storage
• https://68232--docspreview.netlify.app/openshift-enterprise/latest/scalability_and_performance/optimization/optimizing-storage#logging

QE review:

• QE has approved this change.

Additional information: Not sure who the current maintainer of the parent page is, this is a change to the logging info only.

[ocpdocs-previewbot]

🤖 Updated build preview is available at:
https://68232--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/34255

[libander]

@periklis / @xperimental / @btaani - SME review please.

[libander]

@QiaolingTang / @anpingli / @kabirbhartiRH - QE Review please.

[libander]

/label peer-review-needed

[JoaoBraveCoding]

lgtm, from my side

[btaani]

/lgtm

[kabirbhartiRH]

/lgtm

[openshift-ci]

@mletalie: The label(s) /label peer-review-in-process cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, rebase/manual, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, cloud-experts, cnv, dev-tools, distributed-tracing, ims, jira/valid-bug, merge-review-in-progress, merge-review-needed, mtc, multi-arch, oadp, peer-review-done, peer-review-in-progress, peer-review-needed, rhacs, rhv, sd-docs, serverless, service-mesh, sme-review-done, sme-review-needed, staff-eng-approved, telco. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label peer-review-in-process

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mletalie]

/label peer-review-in-progress

[mletalie]

Hello @libander
Had a couple of suggestions, otherwise LGTM! Thanks!

[mletalie]

/remove-label peer-review-in-progress
/remove-label peer-review-needed
/label peer-review-done

[openshift-ci]

New changes are detected. LGTM label has been removed.

[libander]

/label merge-review-needed

[stevsmit]

/cherry-pick enterprise-4.12

[stevsmit]

/cherry-pick enterprise-4.13

[stevsmit]

/cherry-pick enterprise-4.14

[stevsmit]

/cherry-pick enterprise-4.15

[openshift-cherrypick-robot]

@stevsmit: new pull request created: #68283

In response to this:

/cherry-pick enterprise-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@stevsmit: new pull request created: #68284

In response to this:

/cherry-pick enterprise-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@stevsmit: new pull request created: #68285

In response to this:

/cherry-pick enterprise-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@stevsmit: new pull request created: #68286

In response to this:

/cherry-pick enterprise-4.15

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@stevsmit: new pull request could not be created: failed to create pull request against openshift/openshift-docs#enterprise-4.12 from head openshift-cherrypick-robot:cherry-pick-68232-to-enterprise-4.12: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-68232-to-enterprise-4.12."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

In response to this:

/cherry-pick enterprise-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@stevsmit: new pull request could not be created: failed to create pull request against openshift/openshift-docs#enterprise-4.13 from head openshift-cherrypick-robot:cherry-pick-68232-to-enterprise-4.13: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-68232-to-enterprise-4.13."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

In response to this:

/cherry-pick enterprise-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.