Openshift Cluster CIDR range not configured to 10.128.0.0/14

Ajith Anilkumar 0 Reputation points
2023-03-17T13:49:30.56+00:00

I have deployed an Azure Redhat Openshift Cluster. I have seen that by default the pod cidr ranges are supposed to be 10.128.0.0/14. But after deployment , my openshift cluster has the pod cidr in the range of 10.100.0.0/14. I have critical external resources which have IPs in this range. I am not able to connect to these IP from inside my cluster.

Is there a solution for this without redeploying the cluster? Is it possible to change the pod cidr range after the cluster is deployed? Even if i redeploy, is there a way i can specify the pod cidr ranges?

Thanks

Azure Red Hat OpenShift
Azure Red Hat OpenShift
An Azure service that provides a flexible, self-service deployment of fully managed OpenShift clusters.
80 questions
{count} votes

1 answer

Sort by: Most helpful
  1. deherman-MSFT 34,436 Reputation points Microsoft Employee
    2023-03-20T18:42:45.42+00:00

    @Ajith Anilkumar

    I understand you have deployed an Azure Redhat Openshift Cluster but see that the Pod CIDR is 10.100.0.0/14 instead of the expected 10.128.0.0/14.

    The Pod CIDR and Service CIDR can both be modified during the deployment if using the ARM template. See here for an example template which has these parameters.

    Modifying these CIDRs for the SDN should be possible. The cluster administrators can control pod network settings on master hosts by modifying parameters in the networkConfig section of the master configuration file (located at /etc/origin/master/master-config.yaml by default). The OpenShift documentation goes over this configuration in detail.

    Hope this helps! Let me know if you still have questions and I will be happy to assist.


    Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments