Skip to content

update the alert runbook to guide 4.13+ clusters to expand network range #310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
bmeng wants to merge 1 commit into from
Closed

update the alert runbook to guide 4.13+ clusters to expand network range #310

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions alerts/cluster-network-operator/V4SubnetAllocationThresholdExceeded.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,9 +33,17 @@ Count the number of nodes to compare.

## Mitigation

### For clusters running prior to 4.13

We do not support adding additional cluster networks for ovn-kubernetes.

User will have to create a new cluster for more worker nodes.

Choosing a larger cluster network CIDR which can hold more subnets could prevent
this happening.

### For clusters running with version 4.13 onward

User can follow the OpenShift document to expand the cluster subnet IP address range.

Refer: https://docs.redhat.com/en/documentation/openshift_container_platform/4.13/html/release_notes/ocp-4-13-release-notes#ocp-4-13-expand-cluster-network-ip-address-range_release-notes