Control Plane latency recommendations for reliable clusters

[shahsahil264]

Version(s): 4.15+

Issue: https://issues.redhat.com/browse/CHAOS-832

Link to docs preview:

🤖 Thu Jul 11 11:51:50 - Prow CI generated the docs preview:

https://78769--ocpdocs-pr.netlify.app/

QE review:

• QE has approved this change.

Additional information:

[ocpdocs-previewbot]

🤖 Tue Feb 25 17:11:11 - Prow CI generated the docs preview:

https://78769--ocpdocs-pr.netlify.app/

[shahsahil264]

@openshift/team-documentation

[shahsahil264]

@chaitanyaenr

[shahsahil264]

@ahardin-rh PTAL. Thanks.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[shahsahil264]

/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

[shahsahil264]

/lifecycle frozen

[openshift-ci]

@shahsahil264: The lifecycle/frozen label cannot be applied to Pull Requests.

In response to this:

/lifecycle frozen

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.

[chaitanyaenr]

/reopen

[openshift-ci]

@chaitanyaenr: Reopened this PR.

In response to this:

/reopen

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.

[chaitanyaenr]

@rpattath @ahardin-rh PTAL when you get a chance. Thanks!

[shahsahil264]

Thanks for all the suggestions @stevsmit !!

I have made the changes as suggested

[openshift-ci]

@shahsahil264: 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.

[shahsahil264]

@rpattath @paigerube14

[chaitanyaenr]

/lgtm

[bergerhoffer]

The branch/enterprise-4.20 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.19. And any PR going into main must also target the latest version branch (enterprise-4.20).

If the update in your PR does NOT apply to version 4.20 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[chaitanyaenr]

/remove-lifecycle stale.

[chaitanyaenr]

@stevsmit need your review when you get a chance. Thanks!

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[bergerhoffer]

The branch/enterprise-4.21 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.20. And any PR going into main must also target the latest version branch (enterprise-4.21).

If the update in your PR does NOT apply to version 4.21 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

[chaitanyaenr]

Thanks for the feedback @bergerhoffer, appreciate it! @shahsahil264 let's target it PR againt enterprise 4.21 instead of main given that the content is applicable. Thoughts?

[chaitanyaenr]

/remove-lifecycle rotten

[bergerhoffer]

@chaitanyaenr You do not need to change this target away from main unless the update is only applicable to an older version. For example, if the update only applied to version 4.15, then you would target this only to enterprise-4.15.

But as long as this still applies to the newest version (4.21), then you can keep this PR targeting main.