I have ECK Elasticsearch and Kibana running in k8s (Azure). One pod of each.
I made a user with *bin/elasticsearch-users useradd test123 -p 123456 -r superuser *
The Kibana UI (and the corresponding Elasticsearch API) only shows users from the Native realm, as those are the only users that can be managed via the cluster.
The user that you created with elasticsearch-users is in the File realm, which is different and cannot be managed via the UI or API.
Generally we recommend that users are created in the native realm rather than the file realm. If you have a small number of service accounts that you want to manage as code (or you want them to be available before the cluster fully forms), then you can use the file realm for that, but the tradeoff is that you have to use the CLI tooling to manage them.
Since ECK 1.1.0, file realm users and roles are configurable using Kubernetes secrets. This notably enables consistent and auditable user management practices and GitOps use cases.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.