argo-events calendar gateway/trigger/workflow from documentation not working.

[ttelfer]

Describe the bug Followed quick start guide:

https://github.com/argoproj/argo-events/blob/master/docs/quickstart.md

-Running basic hello world workflow works.

Then followed the guide for calendar gateway/sensor:

https://github.com/argoproj/argo-events/blob/master/docs/tutorial.md#calendar

There are no workflows in argo list after many minutes of waiting.

Expected behavior Expected workflows to run. argo listshows nothing.

Environment (please complete the following information):

• Azure AKS
• Kubernetes 1.10.8

Any help would be greatly appreciated. Also let me know if I can provide any additional information.

[VaibhavPage]

Are gateway, gateway-configmap and sensor deployed in same namespace as gateway controller and sensor controller?

[ttelfer]

@VaibhavPage Thanks for responding. How would I check that?

I also just tried rerunning the kubectl commands:

kubectl create --namespace=argo-events -f ...

Still nothing.

[VaibhavPage]

Can you post the logs of sensor-controller and gateway-controller?

[VaibhavPage]

Also did you switch namespace to argo-events after performing kubectl create namespace argo-events and before creating sensor and gateway controllers?

[ttelfer]

@VaibhavPage forgive me I'm fairly new to argo and kubernetes. I don't remember switching namespaces. From what I read in the kubectl documentation using kubectl create --namespace creates it in the given namespace. Is that correct?

Also, what command would I run to get logs from the two controllers you mentioned?

[VaibhavPage]

it looks like sensor and gateway controller are created in default namespace. You can first start by deploying them in argo-events by executing following commands

kubectl create -n argo-events -f hack/k8s/manifests/sensor-controller-configmap.yaml
kubectl create -n argo-events -f hack/k8s/manifests/sensor-controller-deployment.yaml
kubectl create -n argo-events -f hack/k8s/manifests/gateway-controller-configmap.yaml
kubectl create -n argo-events -f hack/k8s/manifests/gateway-controller-deployment.yaml

Once these configmaps and deployments are created, can you post output of:

kubectl -n argo-events get deployements
kubectl -n argo-events get configmaps

Tip: there is nice utility called kubectx https://github.com/ahmetb/kubectx which let you switch your kubectl context and namespace easily

As you have already created gateway, gateway configmap and sensor in argo-events namespace, gateway and sensor controllers should pick these up.

[ttelfer]

That did it! Thanks for your help. It seems like the documentation may need to be updated.

Also, thank you for the utility.

[VaibhavPage]

I'll add note on switching namespace in next PR.