Update logging-loki-zone-aware-rep.adoc #83376
Conversation
corrected size 1x.extra-small
openshift-ci
bot
added
the
size/XS
| = Zone aware data replication | ||
|
|
||
| In the {logging} 5.8 and later versions, the {loki-op} offers support for zone-aware data replication through pod topology spread constraints. Enabling this feature enhances reliability and safeguards against log loss in the event of a single zone failure. When configuring the deployment size as `1x.extra.small`, `1x.small`, or `1x.medium,` the `replication.factor` field is automatically set to 2. | ||
| In the {logging} 5.8 and later versions, the {loki-op} offers support for zone-aware data replication through pod topology spread constraints. Enabling this feature enhances reliability and safeguards against log loss in the event of a single zone failure. When configuring the deployment size as `1x.extra-small`, `1x.small`, or `1x.medium,` the `replication.factor` field is automatically set to 2. |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'in case', 'if', or 'when' rather than 'in the event'. For more information, see RedHat.TermsErrors.
|
@nikijain30: all tests passed! Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
|
/label peer-review-needed |
openshift-ci
bot
added
the
peer-review-needed
adellape
added
peer-review-done
|
@nikijain30 Per:
Does this mean it should not go into 4.17 and 4.18? If that's the case, then these should be individual PRs against those branches, and should not go into If this actually can just be 4.14+ (and therefore get picked to 4.17 and 4.18), then this is fine to proceed as is. |
Hi @adellape Thank you for checking this, Change is required on all versions lower than 4.17. (from 4.11 to 4.16) Shall I create new PR for each of them ? |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci
bot
added
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. In response to this:
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-sigs/prow repository. |
5 participants
corrected size 1x.extra-small
Version(s):
4.16 , 4.15, 4.14Issue:
https://issues.redhat.com/browse/OBSDOCS-1377Link to docs preview:
https://83376--ocpdocs-pr.netlify.app/openshift-dedicated/latest/observability/logging/log_storage/cluster-logging-loki.html
https://83376--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/log_storage/cluster-logging-loki.html
https://83376--ocpdocs-pr.netlify.app/openshift-rosa/latest/observability/logging/log_storage/cluster-logging-loki.html
QE review:
Additional information: