sync-catalog: pod won't start if consul --> k8s sync is disabled

[jackpizarro]

Installed with the Helm chart.

      containers:
      - command:
        - /bin/sh
        - -ec
        - |
          consul-k8s sync-catalog \
            -http-addr=${HOST_IP}:8500 \
            -to-k8s=true \
            -consul-domain=consul \
            -k8s-write-namespace=${NAMESPACE}

That works fine:

2018-10-03T01:27:51.961Z [INFO ] to-k8s/sink: starting runner for syncing
2018-10-03T01:27:51.961Z [INFO ] to-consul/source: starting runner for endpoints
2018-10-03T01:27:51.966Z [INFO ] to-k8s/source: received services from Consul: count=1
2018-10-03T01:27:52.061Z [INFO ] to-consul/source.controller/endpoints: initial cache sync complete
2018-10-03T01:27:52.061Z [INFO ] to-k8s/controller: initial cache sync complete

But if I change the deployment to '-to-k8s=false' I get this:

2018-10-03T01:24:53.516Z [INFO ] to-consul/source: starting runner for endpoints
2018-10-03T01:24:53.522Z [INFO ] to-consul/sink: ConsulSyncer quitting
ERROR: logging before flag.Parse: E1003 01:24:53.522913       8 controller.go:115] Error syncing cache
ERROR: logging before flag.Parse: E1003 01:24:53.522960       8 controller.go:115] Error syncing cache

And it stays in CrashLoopBackOff.