-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Breaking change] kibana
user removed and replaced by kibana_system
#81680
Comments
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
kibana
user removed and replaced by kibana_system
user
kibana
user removed and replaced by kibana_system
userkibana
user removed and replaced by kibana_system
Pinging @elastic/kibana-security (Team:Security) |
I'm going to remove the |
We have not actually removed the I updated the issue description to clarify that we won't be breaking this in 8.0. |
Change description
Which release will ship the breaking change?
8.0(Edit Joe 9/1/21: this is deprecated but we are not yet sure when we will remove it)Describe the change. How will it manifest to users?
Thekibana
user has been removed, and users should use thekibana_system
user instead. Instances of Kibana that are configured to use thekibana
will not be able to start-up.(Edit Joe 9/7/21: we should encourage users to use a service account token instead, if possible. Need to find out if this can be done when accessing Elasticsearch without TLS in 7.16)
How many users will be affected?
I anticipate an overwhelming majority of users will still be using the
kibana
user. Thekibana_system
user was only recently added, and unless users are in the habit of reading the Kibana deprecation logs, they're likely unware of this change.What can users do to address the change manually?
Use Kibana's user management to set the password for the
kibana_system
user, and update allkibana.yml
's to use this username and password for theelasticsearch.username
andelasticsearch.password
.How could we make migration easier with the Upgrade Assistant?
There isn't a good way to use the Upgrade Assistant to do so. We don't want the Kibana server to be able to write values to the
kibana.yml
, nor do we have a way of doing so across every instance of Kibana.Are there any edge cases?
No
Test Data
Example
kibana.yml
:Cross links
This is related to #51101.
The text was updated successfully, but these errors were encountered: