consul-sync-catalog doesn't start when toK8s is false

[jondeandres]

We don't want, for now, to register Consul services as K8s services (we are just reaching those using service_name.service.domain), so we are using this config:

syncCatalog:
  # True if you want to enable the catalog sync. "-" for default.
  enabled: true
  image: null

  # toConsul and toK8S control whether syncing is enabled to Consul or K8S
  # as a destination. If both of these are disabled, the sync will do nothing.
  toConsul: true
  toK8S: false

However, having toK8S: false makes consul-sync-catalog not to start:

consul-sync-catalog-644884767d-b97bn   0/1       Error     2         19s
consul-sync-catalog-644884767d-b97bn   0/1       CrashLoopBackOff   2         20s
consul-sync-catalog-644884767d-b97bn   0/1       Error     3         48s
consul-sync-catalog-644884767d-b97bn   0/1       CrashLoopBackOff   3         1m
consul-sync-catalog-644884767d-b97bn   0/1       Error     4         1m
consul-sync-catalog-644884767d-b97bn   0/1       CrashLoopBackOff   4         1m
consul-sync-catalog-644884767d-b97bn   1/1       Running   5         2m
consul-sync-catalog-644884767d-b97bn   0/1       Error     5         2m
consul-sync-catalog-644884767d-b97bn   0/1       CrashLoopBackOff   5         3m

The logs for thad pod are:

➜  ~ kubectl logs -f  consul-sync-catalog-644884767d-k6th9                                                                                                                      
2018-10-11T05:38:31.376Z [INFO ] to-consul/sink: ConsulSyncer quitting
ERROR: logging before flag.Parse: E1011 05:38:31.377307       6 controller.go:115] Error syncing cache                                                                          
2018-10-11T05:38:31.378Z [INFO ] to-consul/source: starting runner for endpoints
ERROR: logging before flag.Parse: E1011 05:38:31.378587       6 controller.go:115] Error syncing cache                                                                          

When toK8S: true K8s services are registered in Consul correctly, but as I explained, we don't want Consul to K8S to be synced. We are not using CoreDNS for now and it seems it's required for toK8S

[tomwganem]

The issue to track is hashicorp/consul-k8s#7

[jondeandres]

oh, thanks @tomwganem, didn't see that, I close this