Default installation configs does not provide a working login

[caiobegotti]

Just installed it and tried to open the Kibana dashboard and then got this:

 Login is currently disabled. Administrators should consult the Kibana logs for more details. 

The login form is non-interactive and I cannot log in. The pod logs only show 200 OKs until that.

[caiobegotti]

Apparently this is because ES is not up but after taking a look at it to me there is some bug in the chart because not all .yaml files from templates/ are being properly loaded and set up (namely ES StatefulSet):

$ helm install . -n efk
NAME:   efk
LAST DEPLOYED: Sun Aug 12 10:42:09 2018
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1/Pod(related)
NAME                         READY  STATUS             RESTARTS  AGE
efk-kibana-6845f75c4b-qr7g4  0/1    ContainerCreating  0         3s

==> v1/ConfigMap
NAME                              DATA  AGE
efk-fluentd-elasticsearch-config  6     3s

==> v1/Service
NAME               TYPE       CLUSTER-IP     EXTERNAL-IP  PORT(S)   AGE
efk-elasticsearch  ClusterIP  10.15.240.45   <none>       9200/TCP  3s
efk-kibana         ClusterIP  10.15.255.123  <none>       5601/TCP  3s

==> v1beta2/Deployment
NAME        DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
efk-kibana  1        1        1           0          3s


NOTES:
1. Get the application URL by [...]

[caiobegotti]

Oh! It only works with RBAC enabled then? If it by design or a bug in the templates @GrantKlassy / @andrzejwp?

[krishnaarava]

Does this work with RBAC enabled? Can the README be updated to reflect the new instructions?

[yobitelcom]

I'm facing the same error. Please help me to sort out it.