Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fail at startup if the current node version is not exactly the same as .node-version #17456

Closed
epixa opened this issue Mar 29, 2018 · 2 comments
Closed

Fail at startup if the current node version is not exactly the same as .node-version #17456

epixa opened this issue Mar 29, 2018 · 2 comments
Labels
release_note:enhancement Team:Operations Team label for Operations Team

Comments

@epixa
Copy link
Contributor

epixa commented Mar 29, 2018

We only officially support Kibana running against the exact node version that we list in .node-version, but we have no enforcement for this in the product itself. To help folks avoid being in a situation where Kibana is not going to be behave in expected ways, or worse in a situation where their Kibana install has security vulnerabilities due to an incompatible node version, we should fail to start Kibana if the node version is not an exact match.
@epixa epixa added release_note:enhancement Team:Operations Team label for Operations Team labels Mar 29, 2018
@epixa
Copy link
Contributor Author

epixa commented Mar 29, 2018

@elastic/kibana-operations

@jbudz
Copy link
Member

jbudz commented Oct 23, 2018

Done with #19154

@jbudz jbudz closed this as completed Oct 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
release_note:enhancement Team:Operations Team label for Operations Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@epixa @jbudz