It is easier to just add a CPU to get 30 pods.

With the Istio components taking 9 pods, it is pretty easy to hit the 20
limit :-)





On Fri, Nov 17, 2017 at 11:46 PM, Andrew Block <[email protected]> wrote:

> Burr,
>
> Heres a one liner that will modify the pods per core value (30 in this use
> case) in minishift
>
> minishift ssh "sudo sed -i '/kubeletArguments/ a \  pods-per-core:'
> /var/lib/minishift/openshift.local.config/node-localhost/node-config.yaml
> && sudo sed -i '/pods-per-core/ a \    - \"30\"'
> /var/lib/minishift/openshift.local.config/node-localhost/node-config.yaml
> && sudo docker restart origin"
>
>
>
> On Fri, Nov 17, 2017 at 11:11 AM, Hugo Guerrero <[email protected]>
> wrote:
>
>> I believe options are not in the file by defaul, but look for
>> "kubeArguments" section and add them there.
>>
>>
>> *Hugo*
>>
>> On Fri, Nov 17, 2017 at 11:33 AM, Burr Sutter <[email protected]> wrote:
>>
>>>
>>>
>>> On Fri, Nov 17, 2017 at 10:25 AM, Hugo Guerrero <[email protected]>
>>> wrote:
>>>
>>>> Well, so minishift ships with the default values for both documented
>>>> kubeArguments. The important one is the pods-per-core as "10" is the
>>>> default value. So if you start your minishift with just 2 cores that's the
>>>> max ammount of pods you will get as the "the lower of the two limits
>>>> the number of pods on a node". No matter how many max-pods you put, you
>>>> still we limited by pods-per-core. So if you add more cores you will get
>>>> more pods available up to "max-pods". Or just change the pods-per-core and
>>>> still use the same amount of cpus.
>>>>
>>>> The editing place is on /var/lib/minishift/openshif
>>>> t.local.config/node-localhost/node-config.yaml unless you modified it
>>>> in the start command.
>>>>
>>>
>>> I see that file on my minishift but line do I edit?
>>> I do not see a pods-per-core entry
>>>
>>> and once edited, do I need to "restart" something to get the setting to
>>> take effect.
>>>
>>>
>>>>
>>>> *Hugo*
>>>>
>>>> On Fri, Nov 17, 2017 at 9:37 AM, Burr Sutter <[email protected]>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, Nov 16, 2017 at 10:06 PM, Hugo Guerrero <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> Hi
>>>>>>
>>>>>> Burr, the default size of the minishift VM is just 1 core and 4GB
>>>>>> ram, you will run out of pods easily as it will support max 20 pods. You
>>>>>> can increase the cores associated with the VM and the memory to allow 
>>>>>> more
>>>>>> pods to be deployed. I just added 4 cores instead of 1 and was able to
>>>>>> deploy all my pods.
>>>>>>
>>>>>
>>>>> There is still a fixed 20 pod limit for the Node as demonstrated by
>>>>> Graham's url to the docs.
>>>>>
>>>>> oc describe node allows you to see all the pods and the fact that I am
>>>>> at the limit.
>>>>>
>>>>> I am just not sure how to change the variable.
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> *Hugo*
>>>>>>
>>>>>> On Thu, Nov 16, 2017 at 6:56 PM, Burr Sutter <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>> I finally figured out why I had pods that would not deploy, there is
>>>>>>> a 20 pod max on minishift.
>>>>>>>
>>>>>>> Has anyone seen a way to tweak that limit?
>>>>>>>
>>>>>>> And can you update it on a live system?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Have a question?
>>>>>>> First, check the FAQ: https://pnt.redhat.com/pnt/p-7
>>>>>>> 34673/openshift-con...-Jun-2017.pdf
>>>>>>> Next, check the archives: http://post-office.corp.redhat
>>>>>>> .com/archives/openshift-sme/
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>> Have a question?
>> First, check the FAQ: https://pnt.redhat.com/pnt/p-7
>> 34673/openshift-con...-Jun-2017.pdf
>> Next, check the archives: http://post-office.corp.redhat
>> .com/archives/openshift-sme/
>>
>
>
>
> --
> Andrew Block
> Principal Consultant | Red Hat Consulting
> 101 N. Wacker, Suite 150
> <https://maps.google.com/?q=101+N.+Wacker,+Suite+150Chicago,+IL+60606&entry=gmail&source=g>
> Chicago, IL 60606
> <https://maps.google.com/?q=101+N.+Wacker,+Suite+150Chicago,+IL+60606&entry=gmail&source=g>
> [email protected] | m. (716) 870-2408
>
>
_______________________________________________
Devtools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/devtools

Reply via email to