Issues running install from brew.

[argais]

I just installed it from brew and the software just hang there if I use any flags..
e.g.

kube-system/calico-node-gd4xx[calico-node]: 2017-11-02 14:09:32.803 [INFO][89] int_dataplane.go 674: Applying dataplane updates
2017-11-02 14:09:32.803 [INFO][89] ipsets.go 224: Asked to resync with the dataplane on next update. family="inet"
2017-11-02 14:09:32.803 [INFO][89] ipsets.go 224: Asked to resync with the dataplane on next update. family="inet6"
2017-11-02 14:09:32.803 [INFO][89] ipsets.go 255: Resyncing ipsets with dataplane. family="inet"
2017-11-02 14:09:32.803 [INFO][89] ipsets.go 255: Resyncing ipsets with dataplane. family="inet6"
2017-11-02 14:09:32.805 [INFO][89] ipsets.go 297: Finished resync family="inet6" numInconsistenciesFound=0 resyncDuration=1.595033ms
2017-11-02 14:09:32.805 [INFO][89] ipsets.go 297: Finished resync family="inet" numInconsistenciesFound=0 resyncDuration=1.841668ms
2017-11-02 14:09:32.806 [INFO][89] int_dataplane.go 689: Finished applying updates to dataplane. msecToApply=2.152992
kube-system/calico-node-tqnbw[calico-node]: 2017-11-02 14:09:34.229 [INFO][91] int_dataplane.go 674: Applying dataplane updates
2017-11-02 14:09:34.229 [INFO][91] ipsets.go 224: Asked to resync with the dataplane on next update. family="inet"
2017-11-02 14:09:34.229 [INFO][91] ipsets.go 224: Asked to resync with the dataplane on next update. family="inet6"```
Works just fine right?

Now..

➜ kail --pod kube-system/calico
^C%
~ took 1m 40s

Am I doing it wrong? 

running on macOs 10.13.1, lemme know if I can provide any other info to help find out what is going on.

[boz]

Hi @argais . If you use --pod <NAME>, you have to use the full name. It looks like you're trying to match calico-node-gd4xx, so you can use --pod calico-node-gd4xx or --pod kube-system/calico-node-gd4xx.

That being said, kail should allow you to not worry about things like the random -gd4xx suffix. For instance, you can use --ns kube-system to match pods only in the kube-system namespace, and if your pod is started by a daemonset, replicaset, deployment, etc... there are options for matching pods created by those objects (if your daemonset is named 'calico-node', you can use --ds calico-node).

Also, instead of waiting for log output, you can use --dry-run to see which pods are matched.

[argais]

hah! totally missed the dry-run argument in there :P

I still feel I'm missing something.

So from what you said, I should be able to filter by a given deployment too right? but I still cant seem to get a match.

➜ kubectl -n kube-system get deploy nginx-ingress-controller-internal
NAME                                DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
nginx-ingress-controller-internal   3         3         3            3           30d
➜ kail --deploy kube-system/nginx-ingress-controller-internal --dry-run
NAMESPACE NAME CONTAINER NODE
➜ kail --deploy nginx-ingress-controller-internal --ns kube-system --dry-run
NAMESPACE NAME CONTAINER NODE

[boz]

Huh. I'll take a look today to try and reproduce this.

Thanks for the report!

[argais]

Thanks for the quick reply, looking forward to getting this figured out, as it looks like kail will be realllllly handy :)