POD's default CIDR overlaps other external services within network

Solution Verified - Updated

Environment

  • Red Hat OpenShift Container Platform
    • 4
  • Azure Red Hat Openshift (ARO)
    • 4
  • Red Hat OpenShift Service on AWS (ROSA)
    • 4
  • Red Hat OpenShift Dedicated (OSD)
    • 4

Issue

  • Can't connect to services in the corporate network because POD Classless Inter-Domain Routing (CIDR or supernetting) overlaps with other services on our network.
  • Is it possible to change CIDR for pods without recreating the cluster?

Resolution

  • Pod and Service Network CIDRs shouldn't overlap with other address ranges in use on your network. They must not be within the virtual network IP address range of your cluster. Content from docs.microsoft.com is not included.Concepts-networking

  • Since OCP 4.13 the capability of expanding the network IP address range for pods by changing the CIDR has been available. However, you cannot change the network configuration (pod / service / host) within an established OpenShift cluster.

  • You have a choice to Build a new cluster with a network that doesn't conflict with your connected services and migrate to it, or re-network your connected services.

SBR
Product(s)
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.