```
$ kubectl logs controller-0 -n controller-testfaster api-server
[...]
9a364618-ad44-4329-8238-9d9b7644ba21: controller-0 2021-03-23 14:34:55 INFO juju.kubernetes.provider provider.go:98 using in-cluster config
0f017f83-1b8f-42bf-884f-4bbc0acabc3b: application-argo-ui 2021-03-23 14:34:55 INFO unit.argo-ui/0.juju-log server.go:314 Reactive main running for hook update-status
0f017f83-1b8f-42bf-884f-4bbc0acabc3b: application-argo-ui 2021-03-23 14:34:55 INFO unit.argo-ui/0.juju-log server.go:314 Invoking reactive handler: reactive/argo_ui.py:13:charm_ready
0f017f83-1b8f-42bf-884f-4bbc0acabc3b: application-argo-ui 2021-03-23 14:34:55 INFO unit.argo-ui/0.juju-log server.go:314 status-set: active: 
0f017f83-1b8f-42bf-884f-4bbc0acabc3b: application-argo-ui 2021-03-23 14:34:55 INFO juju.worker.caasoperator.uniter.argo-ui/0.operation runhook.go:145 ran "update-status" hook (via explicit, bespoke hook script)
```
this looks healthy in terms of what it's logging, but stuck