update the alert runbook to guide 4.13+ clusters to expand network range #310
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bmeng The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
|
||
| ### For clusters running with version 4.13+ | ||
|
|
||
| User can follow the OpenShift doc to expand the network IP address range. |
There was a problem hiding this comment.
Please use 'document' instead of 'doc'.
There was a problem hiding this comment.
Instead of 'network IP address range', we should say 'cluster subnet IP address range'.
| Choosing a larger cluster network CIDR which can hold more subnets could prevent | ||
| this happening. | ||
|
|
||
| ### For clusters running with version 4.13+ |
There was a problem hiding this comment.
Can you use 'onward' instead of using '+' to imply later versions?
|
|
||
| User can follow the OpenShift doc to expand the network IP address range. | ||
|
|
||
| Refer: https://docs.redhat.com/en/documentation/openshift_container_platform/4.13/html/networking/configuring-cluster-network-range |
There was a problem hiding this comment.
Do you know if this link remains true for all versions? If not, we can probably point to the release note mention for this change.
|
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
|
@bmeng: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
3 participants
No description provided.