Quick solution is to create the minishift profiles with more cpus.
We can also change the pods-per-core limit by patching the node config file
minishift openshift config set --target node --patch
'{"kubeletArguments": { "pods-per-core": ["20"] }
}'
On Sat, Oct 20, 2018 at 10:22 PM Burr Sutter <bsutter(a)redhat.com> wrote:
I notice that "out-of-the-box" we seem to be running 11 pods with Openshift
3.10 via Minishift 1.25
With the 10 pod per core limit, this gives very little room for the end-user to launch
their own pods. When you bring in Istio, it gets even more limited.
oc get pods --all-namespaces
NAMESPACE NAME READY
STATUS RESTARTS AGE
default docker-registry-1-cztks 1/1
Running 0 4m
default persistent-volume-setup-ppzv2 0/1
Completed 0 4m
default router-1-zk284 1/1
Running 0 4m
kube-dns kube-dns-pr5pj 1/1
Running 0 4m
kube-proxy kube-proxy-mt6b9 1/1
Running 0 4m
kube-system kube-controller-manager-localhost 1/1
Running 0 4m
kube-system kube-scheduler-localhost 1/1
Running 0 4m
kube-system master-api-localhost 1/1
Running 1 3m
kube-system master-etcd-localhost 1/1
Running 0 3m
openshift-apiserver openshift-apiserver-bwlbj 1/1
Running 0 4m
openshift-controller-manager openshift-controller-manager-pp7nz 1/1
Running 0 4m
openshift-core-operators openshift-web-console-operator-8cf4ddf7-9rghj 1/1
Running 0 4m
openshift-web-console webconsole-85f96dd597-72n27 1/1
Running 0 3m
_______________________________________________
Minishift Mailing List mailing list -- minishift(a)lists.minishift.io
To unsubscribe send an email to minishift-leave(a)lists.minishift.io
--
ANJAN J NATH
nathearthling.me