OCPBUGS-81283: Document ServiceCIDR expansion not supported#110733
OCPBUGS-81283: Document ServiceCIDR expansion not supported#110733kquinn1204 wants to merge 2 commits intoopenshift:mainfrom
Conversation
Add limitation noting that expanding the service network CIDR post-installation is not supported, even though the upstream Kubernetes ServiceCIDR API is visible in OCP. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
@kquinn1204: This pull request references Jira Issue OCPBUGS-81283, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
🤖 Thu Apr 23 16:35:02 - Prow CI generated the docs preview: |
Update phrasing to explicitly state the ServiceCIDR API is present in the cluster and documented in the API reference, not just "visible." Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
@kquinn1204: all tests passed! 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. |
Summary
[IMPORTANT]admonition toconfiguring-cluster-network-range.adocnoting that expanding the service network CIDR post-installation is not supported, even though the upstream KubernetesServiceCIDRAPI is visible in OCP. The Cluster Network Operator blocks this via aValidatingAdmissionPolicy.nw-operator-cr.adocto explicitly call out thatserviceNetworkis immutable and theServiceCIDRAPI is blocked.Related
Preview: