Hi Charles, this limit can be changed in the node configuration, see: https://docs.openshift.com/container-platform/3.7/admin_guide/manage_nodes.html#admin-guide-max-pods-per-node Looking at https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md#configuration it seems that the configuration file should be available under /var/lib/origin/openshift.local.config with oc cluster up. You can use --use-existing-config argument when restarting your cluster to avoid regenarating the configuration.
Regards, Frédéric On Fri, Feb 2, 2018 at 6:59 AM, Charles Moulliard <[email protected]> wrote: > Hi > > I experiment from time to time such problem on my machine using "oc > cluster up" (openshift origin 3.7.x) > > "0/1 nodes are available: 1 Insufficient pods." > > If I look to the to stats generated by the command "oc get node > localhost", then I can see that the limit of the pods created has been > reached. > > As the convention followed by openshift is to limit the number of the pods > "available" to 10pods/cpu, I'm wondering how we could change this value > when a cluster is started ? > > Regards > > Charles > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > -- *Frédéric Giloux* Senior Middleware Consultant Red Hat Germany [email protected] M: +49-174-172-4661 redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted ________________________________________________________________________ Red Hat GmbH, http://www.de.redhat.com/ Sitz: Grasbrunn, Handelsregister: Amtsgericht München, HRB 153243 Geschäftsführer: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
