Control Plane latency recommendations for reliable clusters #76677
Conversation
|
@openshift/team-documentation |
openshift-ci
bot
added
the
size/S
|
🤖 Thu Jun 27 13:15:00 - Prow CI generated the docs preview: |
openshift-ci
bot
added
size/M
|
@mffiedler @ahardin-rh PTAL. Thanks. |
|
@chaitanyaenr Thank you! |
There was a problem hiding this comment.
Great work @shahsahil264 ! I have a few small items:
- squash your commits and push to origin.
- Tell us what versions of OpenShift this applies to? Typically 4.12+ Add that to your comment 0, the first comment in the PR so we can see it easily.
- When you re-push as I have suggested above, PROW will generate a new preview link. Please put that in Comment 0 if you can please sir. I could not find your updates in the preview that PROW had already generated.
- If you are working from a JIRA, please add that link to Comment 0
I am excited, @shahsahil264 , your work is a wonderful addition to the docs!
modules/control-plane-latency.adoc
Outdated
| [id="control-plane-latency_{context}"] | ||
| = Recommended Control Plane latency for reliable clusters | ||
|
|
||
| It's recommended to ensure that the latency between each of the control plane nodes is within 15ms to ensure performant and reliable cluster. Some of the metrics to keep track of includes etcd gRPC requests latency, fysnc latency and any critical alerts. Here are the PromQL queries: |
There was a problem hiding this comment.
| It's recommended to ensure that the latency between each of the control plane nodes is within 15ms to ensure performant and reliable cluster. Some of the metrics to keep track of includes etcd gRPC requests latency, fysnc latency and any critical alerts. Here are the PromQL queries: | |
| Latency between each of the control plane nodes must be less than 15ms to ensure a well performing and reliable cluster. Some of the metrics to keep track of include etcd gRPC requests latency, fysnc latency and any critical alerts. Here are the PromQL queries: |
With Compliance Operator 1.5.0, users can deploy the Compliance Operator on ROSA HCP. Let's update the documentation to advertise that functionality for profiles that are tested on ROSA HCP.
openshift-merge-robot
added
the
needs-rebase
|
PR needs rebase. 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. |
openshift-ci
bot
added
size/XXL
|
@shahsahil264: The following tests failed, say
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. |
|
Because of the issue on this branch, I am closing this PR and have opened up a new one: #78769 |
Version(s):
4.15+Issue:
https://issues.redhat.com/browse/CHAOS-832Link to docs preview:
QE review:
Additional information: