Can't install chart successfully

[pennyscissors]

I've been trying to install this chart following the instructions in the helm 3 section of the readme, but I'm stuck waiting on etcd pods that won't get past the "pending" status.
Any ideas?

Here are the steps I took:

1. Follow instructions to add the ohmyglb repo
2. Create ohmyglb namespace. Installing the chart doesn't create it and will fail saying it can't find a "ohmyglb" namespace so I manually created it. Seems like this is expected behavior in Helm 3 (Correct me if I'm wrong).
3. Run: helm install --debug ohmyglb ohmyglb/ohmyglb

At this point most of the pods are deployed, but the following etcd pods will get stuck in "pending".

Kubectl get pods output:

NAMESPACE       NAME                                                           READY   STATUS             RESTARTS   AGE
default         ohmyglb-coredns-6b7c98d545-hh8kh                               1/1     Running            0          13m
default         ohmyglb-etcd-operator-etcd-backup-operator-7b7765f455-28m5j    1/1     Running            0          13m
default         ohmyglb-etcd-operator-etcd-operator-5d69b5449d-vktx9           0/1     Pending            0          13m
default         ohmyglb-etcd-operator-etcd-restore-operator-5ccc8fccf5-8fqgg   0/1     Pending            0          13m
ohmyglb         external-dns-5844f58797-pdshk                                  1/1     Running            0          13m
ohmyglb         ohmyglb-7c5d899559-zbwlp                                       1/1     Running            0          13m

ohmyglb-7c5d899559-zbwlp logs:

{"level":"info","ts":1588015395.9359705,"logger":"cmd","msg":"Operator Version: 0.5.6"}
{"level":"info","ts":1588015395.9365296,"logger":"cmd","msg":"Go Version: go1.14"}
{"level":"info","ts":1588015395.9368103,"logger":"cmd","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":1588015395.937081,"logger":"cmd","msg":"Version of operator-sdk: v0.16.0"}
{"level":"info","ts":1588015395.9375331,"logger":"leader","msg":"Trying to become the leader."}
{"level":"info","ts":1588015396.6210973,"logger":"leader","msg":"No pre-existing lock was found."}
{"level":"info","ts":1588015396.6304686,"logger":"leader","msg":"Became the leader."}
{"level":"info","ts":1588015397.2903323,"logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":"0.0.0.0:8383"}
{"level":"info","ts":1588015397.2911112,"logger":"cmd","msg":"Registering Components."}
{"level":"info","ts":1588015399.4246273,"logger":"metrics","msg":"Metrics Service object created","Service.Name":"ohmyglb-metrics","Service.Namespace":"ohmyglb"}
{"level":"info","ts":1588015400.085832,"logger":"cmd","msg":"Could not create ServiceMonitor object","error":"an empty namespace may not be set during creation"}
{"level":"info","ts":1588015400.0861387,"logger":"cmd","msg":"Starting the Cmd."}
{"level":"info","ts":1588015400.0868874,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"gslb-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1588015400.0877016,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"gslb-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1588015400.088064,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"gslb-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1588015400.0884078,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"gslb-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1588015400.0889385,"logger":"controller-runtime.manager","msg":"starting metrics server","path":"/metrics"}
{"level":"info","ts":1588015400.1968875,"logger":"controller-runtime.controller","msg":"Starting Controller","controller":"gslb-controller"}
{"level":"info","ts":1588015400.199356,"logger":"controller-runtime.controller","msg":"Starting workers","controller":"gslb-controller","worker count":1}

Some info that might be useful:
Running in a MacBook Pro
helm v3.2.0
docker desktop v2.2.0.5 (engine v19.03.8 and k8s v1.15.5)

[ytsarev]

@pennyscissors hey Steven, thanks for creating the issue and welcome to the project.

Most probably the issue is related to standard docker-on-mac embedded k8s engine.

Try kubectl describe pod on Pending pods - it should clarify why they cannot be scheduled.

We are using kind for ohmyglb testing, even on the Macs. It enables us to properly test multi-worker and multi-cluster setup.

Check the make deploy-full-local-setup target - it will automatically handle the deployment of two test kind clusters for you

[pennyscissors]

@ytsarev Thank you, I figured it out. In case someone runs into the same issue, the problem was I had previously set docker desktop to use 1 CPU since I was running into problems with it overheating my MacBook Pro. This chart seems to require at least 2 CPU's, so it deployed successfully once I made that change.